Jump to content

M-Pixel

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About M-Pixel

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As long as `/main` is included, for most projects, there's very little to be saved by omitting unused branches. Squashing old history would definitely address this pain point, moreso if it could be done per client repo, instead of forcing everybody to lose that history permanently.
  2. In that case, I'll still need a way to replicate from computer to computer (and, of course, replication package files are a bit too inconvenient for this purpose). I looked into replicating directly between my laptop and desktop by opening port 8084, but it seems that the Cloud installation configures the server to only listen to localhost, and doesn't contain any of the server configuration utilities that I would need to change that. Should I use the Personal Edition installer to get the more robust server features, and then log in with my Cloud credentials?
  3. A repository has become very large. I need to work with the repository on a laptop, so I need distributed, and I need to use as little disk space as I can. It is likely that I will want to reference recent history. It is unlikely that I will have any need to reference ancient history. This is a situation I've found myself in more than once before, and I'd like to find a solution. Nodata is a good start, but not feasible. With Nodata, I can make new commits without an internet connection, but that's it. Better than centralized, but far from distributed. Replicating the data needed to populate all commits on the main branch is excessive, when less than half as much data could sufficiently "hydrate" the last month of commits (e.g. repo is 40gb, workspace is 5gb, there is only ~100MB increase in repo size over the past month, seems like I should be able to have 1 month of fully navigable history with only 5.1GB data). Does anything like this exist, or am I describing functionality that would need to be added?
  4. Freeform Labs has been using Plastic Cloud for years now. It's been great. So great, that I'd like to use Plastic for some personal projects. I could use my existing installation, taking care to replicate only between my computers (and not to the company cloud), but that still leaves me with commits labeled with my company account. That's tolerable, but becomes undesirable should I ever want to graduate a personal project to OSS. I got a Personal license already... But I don't know how to use it. I can't install Personal edition alongside Cloud edition (I have the option to replace or cancel). "Can't have multiple installations" is easily solved with a VM. But VirtualBox + Windows + Plastic is too heavy to run on a laptop, and unnecessarily expensive. So then there's Docker... But the Plastic installer doesn't work in Docker for Windows. So, option 1 is to use Docker, but thay requires figuring out how to get it to install properly in that environment. Option 2: I could use Linux containers, which don't have the installer problem because Codice has already QA'd Plastic in Linux Docker. Ubuntu-on-Windows is heavier than Windows-on-Windows, though, and presents potential filesystem mapping issues. Option 3: I could use Git as my backend, using Git Sync, and a username mapping rule to keep the company name out of the equation. But Git Sync is S L O W compared to a simple replicate. And what other features am I missing out on by passing the changesets through Git? Surely something. Finally, I could write some scripts that shut down Plastic Server, change the credentials, then re-start, whenever I want to switch between personal & company. That sounds like far too much work, though, and wouldn't allow me to use both at once, so I'd hardly consider it a viable option. ... And that's all I could come up with. So, Any other suggestions? To any of the Codice staff, if you wanted to do a hobby project with Plastic, how would you approach this problem? If Docker sounds like an agreeable solution, could I get some help with the installer? Or is there a way to get it in ZIP or MSI form instead? Or do you suggest I go with Git Sync after all?
×
×
  • Create New...