Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various fixes 3 #49

Merged
merged 8 commits into from
Nov 17, 2015
Merged

Various fixes 3 #49

merged 8 commits into from
Nov 17, 2015

Conversation

smellsblue
Copy link
Contributor

Some final changes before RC1.

  • Rotate the log so it doesn't grow too large
  • Save storage version and check it when loading a resource
  • Save storage version and check it when grabbing storage engine
  • Save gemstash version in storage and check it before allowing actions
  • Store multiple files in a single storage resource
  • Save specs with gems in single resource
  • Cache and serve marshalled gemspec

…otate)

I chose 2 logs instead of 1 so if someone pokes around, it's clear the log is rotating
I chose 10mb a bit arbitrarily
This gives us future flexibility to change the storage engine and know if a given resource is out of date
Protect from loading a resource of a newer storage version
…ash version

When loading the storage engine, check the storage version isn't too new
Move marshalled private gem specs to be saved with the gem
Move Gemstash::UpstreamGemName to Gemstash::Upstream::GemName
Use defaults in Gemstash::CLI::Setup path, mainly so tests can alter this safely
Specs that the CLI version checking works ok
Stub defaults to use test path, otherwise setup starts checking against your ~/.gemstash directory
@smellsblue
Copy link
Contributor Author

Merging this now so we can release 1.0.0.pre.1. Any changes from peer review can go out to 1.0.0.pre.2.

smellsblue added a commit that referenced this pull request Nov 17, 2015
@smellsblue smellsblue merged commit 5191669 into master Nov 17, 2015
@smellsblue smellsblue deleted the various-fixes-3 branch November 17, 2015 22:43
@pcarranza
Copy link
Contributor

Ok, finally had a moment to go through it all (quite a "few fixes" you had XD)

Anyway, it looks good, there are a few details that I would like to see ironed, but nothing blocker at all, just style and some things on clarity of code and error messages. Good job man! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants