Versioning your REST API is analogous to the versioning of any other API. Minor changes can be done in place, major changes might require a whole new API. The easiest for you is to start from scratch every time, which is when putting the version in the URL makes most sense. If you want to make life easier for the client you try to maintain backwards compatibility, which you can do with deprecation (permanent redirect), resources in several versions etc. This is more fiddly and requires more effort. But it's also what REST encourages in "Cool URIs don't change".
The self-titled series from Stack-On is the most affordable solution for gun security. Although the self-titled series is not fire resistant, it does offer some descent security features as well as a way to keep your entire gun collection in one spot and out of reach from the kiddos. The Stack-On Series comes in 4 different sizes ranging from a small 8-long gun safe all the way up to a mid-sized 36 long-gun safe. Like I said, this one of Stack-On’s most affordable models so there is no reason not to jump up to the 36 long-gun model to allow for expansion.