[PR #256] [CLOSED] Feature: egg meta.update_url field implementation #659

Closed
opened 2026-02-04 18:40:45 +03:00 by OVERLORD · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/panel/pull/256
Author: @a-sync
Created: 5/18/2024
Status: Closed

Base: mainHead: egg-update_url


📝 Commits (1)

  • 80305bc make use of meta.update_url in the clients browser

📊 Changes

1 file changed (+39 additions, -0 deletions)

View changed files

📝 resources/views/admin/eggs/view.blade.php (+39 -0)

📄 Description

A frontend/browser only proof of concept use case for the meta.update_url egg property.
This is how it works:

  1. if the update_url property is available, a "Download from update URL" button appears next to the "Update egg" button
  2. activating the "Download from update URL" button downloads the referenced egg JSON in the browser context, and pre-sets it in the file upload form with a name originated from the exported_at property
  3. activating the "Update egg" button uploads the pre-set file (unless something else was selected)

The only catch is that the host serving the egg JSON must have the proper CORS headers configured for the clients to be able to download the file.
Tested it with success with an egg hosted in a github repo served through raw.githubusercontent.com, jsdelivr.com and statically.io.
update_url poc


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/pelican-dev/panel/pull/256 **Author:** [@a-sync](https://github.com/a-sync) **Created:** 5/18/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `egg-update_url` --- ### 📝 Commits (1) - [`80305bc`](https://github.com/pelican-dev/panel/commit/80305bcdaa3815ccfdd2134206580bf98b900750) make use of meta.update_url in the clients browser ### 📊 Changes **1 file changed** (+39 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `resources/views/admin/eggs/view.blade.php` (+39 -0) </details> ### 📄 Description A frontend/browser only proof of concept use case for the meta.update_url egg property. This is how it works: 1. if the update_url property is available, a "Download from update URL" button appears next to the "Update egg" button 1. activating the "Download from update URL" button downloads the referenced egg JSON in the browser context, and pre-sets it in the file upload form with a name originated from the exported_at property 1. activating the "Update egg" button uploads the pre-set file (unless something else was selected) The only catch is that the host serving the egg JSON must have the proper CORS headers configured for the clients to be able to download the file. Tested it with success with an egg hosted in a github repo served through raw.githubusercontent.com, jsdelivr.com and statically.io. ![update_url poc](https://github.com/pelican-dev/panel/assets/14183614/858ae79a-3293-4afb-b924-e691b9133362) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-04 18:40:45 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel#659