Quick announcement. You may see a notice in Field Kit this coming Monday, May 10, when we push out an update. It should read something like this:
Field Kit 2.0 is coming! To continue using this version, however, we ask that you please migrate to v1.farmos.app so we can begin preparing this site for the big launch. More details can be found on the forum.
So here are said details…
While we’ve never really concluded our beta phase, and so technically don’t have a real version 1.0 to speak of, we decided with the upcoming release of farmOS 2.0 we should shoot towards full compatibility with 2.0 as the launch target for our first stable, general release.
With that taken into consideration, we’d like to reserve the domain farmos.app for that eventual release. We also need to allow for the fact that migration from farmOS 1.x to 2.x will not happen overnight, and for perhaps a much as a year or more, we will want to accommodate two separate user bases running farmOS 1.x and 2.x. Accordingly, we’ll need two concurrently available versions of Field Kit. Finally, to make this transition as smooth as possible, and to avoid Field Kit duplicating the migration logic that’s already in place on the server, . Think of this as basically uninstalling farmos.app, and reinstalling v1.farmos.app (more details below on how to do so).
So to summarize, here’s what you can expect going forward, here’s what you can expect, in summary:
- farmos.app: We will sunset this domain at a date TBD this summer. We will continue posting a warning on that domain, and may at some point disable the ability to create or modify logs and only allow users to sync to their server, to avoid any chance of lost data. We will need to take the site down for a period of time (a week or more) prior to relaunching Field Kit 2.0 on this domain when the time comes.
- v1.farmos.app: This will remain stable and supported for the foreseeable future. We will not be developing new features on this domain, but will provide bug-fixes and other updates so that users can continue using it for as long as they need.
Instructions follow below. Feel free to comment on this topic if you have questions or experience any difficulty.
If your farmOS instance is hosted on Farmier, no need to do anything here! The v1.farmos.app domain has already been added to your server’s default list of trusted apps as of May 3. Proceed to “Migrating on your phone or mobile device” below.
If you are self-hosting, you will likely have v1.farmos.app in your list of defaults so long as you have the latest release of farmOS that includes this commit:
Go to [your-farmOS-hostname]/admin/config/farm/access and confirm that
https://v1.farmos.app is in the list. If it isn’t add it to the bottom and click “Save configuration”.
- Make sure you’ve enabled v1.farmos.app on your server, as described above.
- Sync all logs from https://farmos.app on your device.
- Login to your farmOS server directly (eg, https://test.farmos.net/farm/logs/all) to check that all logs and their data have been synced.
- Go to https://v1.farmos.app, login to your server and sync. You can also re-add the app to your homescreen, which is recommended but optional.
- Logout of https://farmos.app on your device and uninstall the app from your homescreen if you’d done so previously . THIS STEP CANNOT BE UNDONE, SO MAKE SURE YOU’VE COMPLETED STEPS 2 AND 3 BEFOREHAND.
Note: You should be able to distinguish the home screen icon for farmos.app from v1.farmos.app because v1.farmos.app should have the title “farmOS v1”, as opposed to farmos.app which is simply “farmOS”, as seen below.