Earlier today, we released ChronoFrame 1.0.0—our first stable release!
Thank you to everyone who tried ChronoFrame during testing, shared feedback, and contributed. This release brings a redesigned admin dashboard, simpler setup, more privacy options, and a range of improvements to uploads and background processing.
Start the app. Let the setup wizard take it from there.
New installations no longer require a preconfigured .env file. Once ChronoFrame is running, the web-based setup wizard walks you through creating an admin account, adding your site information, and configuring storage and maps.
You can then update your site’s name, description, avatar, and more directly from the dashboard whenever you like.
More choice over how you share your memories
Alongside hidden albums, we’ve added password-protected albums, so you can share selected memories with the people you give the password to.
We’ve also added options to remove photo location data and automatically remove it on upload, making it easier to manage location metadata and reduce the risk of unintentionally revealing where a photo was taken.
A little guidance to help you get started
Your feedback during testing helped us identify steps that could be confusing for new users. We’ve added guided tours that introduce uploads, queue management, and common settings as you first explore the dashboard and its pages.
Smoother uploads and background processing
We’ve made substantial improvements to file uploads and the background processing queue. On supported storage providers, media uploads now use concurrent chunks by default. This is currently available for local storage and selected S3 storage services.
You can also adjust the number of queue workers directly from the dashboard, balancing processing speed and resource usage to suit your server.
There are plenty of smaller improvements and fixes, too. You’ll find the full details in the changelog.
If you’re upgrading from an earlier version, please read the upgrade guide and back up your data first. Keep your existing environment variables during the initial upgrade so ChronoFrame can migrate recognized settings, then review your configuration in the dashboard afterward.
We’d also love to see you in our Discord community. Come share your experience, report an issue, suggest an idea, or help us build what comes next.
Thank you to everyone who has used, tested, translated, or contributed code to ChronoFrame. You helped make 1.0 possible, and we look forward to continuing to improve it together.
Replies
Hi everyone!
Earlier today, we released ChronoFrame 1.0.0—our first stable release!
Thank you to everyone who tried ChronoFrame during testing, shared feedback, and contributed. This release brings a redesigned admin dashboard, simpler setup, more privacy options, and a range of improvements to uploads and background processing.
Start the app. Let the setup wizard take it from there.
New installations no longer require a preconfigured .env file. Once ChronoFrame is running, the web-based setup wizard walks you through creating an admin account, adding your site information, and configuring storage and maps.
You can then update your site’s name, description, avatar, and more directly from the dashboard whenever you like.
More choice over how you share your memories
Alongside hidden albums, we’ve added password-protected albums, so you can share selected memories with the people you give the password to.
We’ve also added options to remove photo location data and automatically remove it on upload, making it easier to manage location metadata and reduce the risk of unintentionally revealing where a photo was taken.
A little guidance to help you get started
Your feedback during testing helped us identify steps that could be confusing for new users. We’ve added guided tours that introduce uploads, queue management, and common settings as you first explore the dashboard and its pages.
Smoother uploads and background processing
We’ve made substantial improvements to file uploads and the background processing queue. On supported storage providers, media uploads now use concurrent chunks by default. This is currently available for local storage and selected S3 storage services.
You can also adjust the number of queue workers directly from the dashboard, balancing processing speed and resource usage to suit your server.
There are plenty of smaller improvements and fixes, too. You’ll find the full details in the changelog.
Ready to get started?
Deployment and usage documentation
Upgrade guide
If you’re upgrading from an earlier version, please read the upgrade guide and back up your data first. Keep your existing environment variables during the initial upgrade so ChronoFrame can migrate recognized settings, then review your configuration in the dashboard afterward.
More about this release:
Full changelog
Github Release · v1.0.0
We’d also love to see you in our Discord community. Come share your experience, report an issue, suggest an idea, or help us build what comes next.
Thank you to everyone who has used, tested, translated, or contributed code to ChronoFrame. You helped make 1.0 possible, and we look forward to continuing to improve it together.
Timothy Yin and the contributors