Differences

This shows you the differences between two versions of the page.

--- devdoc:devdoc_create_repository [2011/11/26 17:23]
abelbeck
+++ devdoc:devdoc_create_repository [2024/07/03 14:02] (current)
abelbeck
@@ Line 3: / Line 3: @@
 When creating custom AstLinux images, you can setup a private repository to maintain custom builds after you created an initial image with ./scripts/astlinux-makeimage.
-On a public or private HTTP server, create a file structure similar to:
+On a public or private HTTPS server, create a file structure similar to:
-    beta-firmware-1.x/
+  custom-firmware-1.x/
-    beta-firmware-1.x/net5501
+  custom-firmware-1.x/genx86_64-serial
-    beta-firmware-1.x/net5501/ver
+  custom-firmware-1.x/genx86_64-serial/astlinux-1.5-6096-5c954d.tar.gz
-    beta-firmware-1.x/net5501/astlinux-1.0-5260.tar.gz.sha1
+  custom-firmware-1.x/genx86_64-serial/astlinux-1.5-6096-5c954d.tar.gz.sha1
-    beta-firmware-1.x/net5501/astlinux-1.0-5260.tar.gz
+  custom-firmware-1.x/genx86_64-serial/ver
-    beta-firmware-1.x/geni586-serial
+  custom-firmware-1.x/genx86_64-vm
-    beta-firmware-1.x/geni586-serial/ver
+  custom-firmware-1.x/genx86_64-vm/astlinux-1.5-6074-c9d0c1.tar.gz
-    beta-firmware-1.x/geni586-serial/astlinux-1.0-5256.tar.gz.sha1
+  custom-firmware-1.x/genx86_64-vm/astlinux-1.5-6074-c9d0c1.tar.gz.sha1
-    beta-firmware-1.x/geni586-serial/astlinux-1.0-5256.tar.gz
+  custom-firmware-1.x/genx86_64-vm/ver
+  custom-firmware-1.x/genx86_64
+  custom-firmware-1.x/genx86_64/astlinux-1.5-6075-ca0390.tar.gz
+  custom-firmware-1.x/genx86_64/astlinux-1.5-6075-ca0390.tar.gz.sha1
+  custom-firmware-1.x/genx86_64/ver
-The "ver" file contents is 'astlinux-1.0-5260' and 'astlinux-1.0-5256', (without quotes) respectively.  A directory must exist for each 'board' type you want to maintain.
+The ''genx86_64-serial/ver'' file contents is ''astlinux-1.5-6096-5c954d'' and respectively for the other "ver" files.  The ".tar.gz" and ".tar.gz.sha1" files are generated in your working directory after a successful ''./scripts/build''. A directory must exist for each 'board' type you want to maintain.
+In the AstLinux web interface Prefs Tab, define the "Repository URL:" as:
+  https://bla-bla.tld/custom-firmware-1.x
-In the web interface Prefs Tab, define the Repository URL as:
-  http://bla-bla.tld/beta-firmware-1.x
 then use the System Tab to upgrade.
 Or from the CLI...
-    upgrade-run-image check http://bla-bla.tld/beta-firmware-1.x
+    upgrade-run-image check https://bla-bla.tld/custom-firmware-1.x
-    upgrade-run-image upgrade http://bla-bla.tld/beta-firmware-1.x
+    upgrade-run-image upgrade https://bla-bla.tld/custom-firmware-1.x
+You can manage as many repos as you wish.  For example:
-You can manage as many repos as you wish
+  https://bla-bla.tld/beta-firmware-1.x
-  http://bla-bla.tld/firmware-1.x
-might be used for production images.
+might be used for pre-production images.
+!!Tip ->!! Alternatively, ''s3fs'' can be used to mount S3 object storage used as an [[https://doc.astlinux-project.org/userdoc:tt_s3_object_storage_client#custom_firmware_repository|S3 bucket firmware repository]]