You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maka's Desktop Nightly is now available at https://nightlies.apache.org/maka/desktop/. A few people have tried it and found the downloads quite slow. The macOS and Windows installers are around 120 to 150 MB, and they currently come directly from the Apache Nightlies server.
That website discussion now exists: #4307 covers the rebuild and the project narrative. This thread keeps the delivery question.
The simplest option is for maka.apache.org to provide a download page that links directly to Nightlies. That makes the builds easier to find, but it will not make downloads faster.
Another option is to route the download through the project website and let the ASF website cache serve the file. Apache Pekko uses project-site rewrite rules for some generated Nightly documentation:
That does not prove the same setup will work for 150 MB installers. We do not yet know whether the website cache will store files of this size or whether it will make a noticeable difference.
I do not think we should change the updater or publication workflow based on that assumption. When work on the Maka website starts, we can test one existing installer through a staging URL. If it produces real cache hits and faster downloads, we can then consider using it for the download page and Nightly updater.
The files should still live only on nightlies.apache.org. The website would be an entry point, not another artifact store. Nightlies would also remain clearly marked as developer snapshots, separate from formal Apache Releases.
A few questions:
Should the Maka website become the main place where users find Desktop Nightly builds?
Is it worth testing a website proxy for the large installers?
If the proxy does not help, should we leave delivery as it is and focus on installer size and differential updates instead?
This discussion is only about the direction. There is no implementation PR yet.
Drafted with OpenAI Codex at the contributor's direction and reviewed by the contributor of record.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Maka's Desktop Nightly is now available at https://nightlies.apache.org/maka/desktop/. A few people have tried it and found the downloads quite slow. The macOS and Windows installers are around 120 to 150 MB, and they currently come directly from the Apache Nightlies server.
That website discussion now exists: #4307 covers the rebuild and the project narrative. This thread keeps the delivery question.
The simplest option is for
maka.apache.orgto provide a download page that links directly to Nightlies. That makes the builds easier to find, but it will not make downloads faster.Another option is to route the download through the project website and let the ASF website cache serve the file. Apache Pekko uses project-site rewrite rules for some generated Nightly documentation:
That does not prove the same setup will work for 150 MB installers. We do not yet know whether the website cache will store files of this size or whether it will make a noticeable difference.
I do not think we should change the updater or publication workflow based on that assumption. When work on the Maka website starts, we can test one existing installer through a staging URL. If it produces real cache hits and faster downloads, we can then consider using it for the download page and Nightly updater.
The files should still live only on
nightlies.apache.org. The website would be an entry point, not another artifact store. Nightlies would also remain clearly marked as developer snapshots, separate from formal Apache Releases.A few questions:
This discussion is only about the direction. There is no implementation PR yet.
Drafted with OpenAI Codex at the contributor's direction and reviewed by the contributor of record.
All reactions