Jump to content

Meceka

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Meceka

  • Rank
    Newbie

Contact Methods

  • Website URL
    www.simulagames.com
  1. Hello. All 3 of our development devices have a fast SSD and a HDD (or slow SSD) and we always used symlink to move databases to secondary drives to save space in primary drive. We didn't have any problem because of that. But of course I would prefer a native support.
  2. Hi Carlos, I would also ask a way to get rid of deleted assets that take space in the database. For example textures that are deleted in 2018 still take space in the database including their revisions. We should be given a choice to get rid of them and their revisions in the database. For our case, we can get rid of all of them that are so old. There is for example a demo scene (including textures and models) of a Unity Asset that we added to version control by mistake. We deleted it in some changeset but now there isn't an easy way to get rid of it from the database. And there is no reason for us to keep it. Thanks, Mehmet
  3. Hi. We have a laptop that we use out-of-office and also in expo's and its not secure for our source code. We delete the Repository folder for such events and re-create it afterwards with Plastic SCM, but I just realized that local distributed copy of PlasticSCM doesn't have encryption applied, so it can be easily used to recreate the source code. I mean the database thats in this directory C:\Program Files\PlasticSCM5\server\jet Is there a way to encrypt this local copy just like it's done in the cloud? Thanks, Mehmet
  4. Can you please briefly explain how I can do this workaround now? I am not an expert. I guess I already have a cloned repo as I am a Plastic Cloud user working distributed. But how do I trim the data? Thank you.
  5. Hello. We are using Plastic SCM Cloud with Unity for 1,5 years now and database size is growing up by time, although our Repository size doesn't increase at all. This happens because the database (and cloud storage) keeps multiple versions of all assets. For example we have 50+ versions of our scene assets and they are really big. And we almost never need the older versions of scenes. We no longer need the histories of most assets from 1 year ago. We currently have 600 changesets but the changesets 1 to 400 aren't required anymore. As I know there was a trim command to delete old changesets from the database, but I couldn't find any info about this in the documentation. In example, to delete all changesets from 1 to 400 and database would look like it started in changeset 401, keeping all changesets to 600. And I guess we can backup and locally keep the original database from our disk. And if we ever need a file from those early changesets, we can access it with plastic using those backups. (From this directory: C:\Program Files\PlasticSCM5\server\jet) Am I correct with these? And if there is such an operation available, whats it called? Are there some best practices on what to do with such scene files that are changed often, but old versions aren't important? What should we do to avoid them growing the database size so fast? Thank you,
×
×
  • Create New...