LivelyKernel / LivelyKernel/lively.next
passing parameters in the URL to a Lively Project
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the Feature**
Configuring a web application for a specific environment is typically done by passing in the configuration variables in either the header or in the URL. I can do this by hand (`http://127.0.0.1:9011/projects/load?name=engageLively--galyleo-dashboard&foo=bar`) which is what I do today, but it would be nice if there was a simple table editor which could be clicked on for a project to configure these.
**Graphics**
Running a Docker image from Docker desktop brings up this dialog:

Clicking on Optional Settings brings up a config dialog:

For HTTP parameters, Postman has a an extensive set of config options;

**Implementation Details**
If applicable, provide insights with regards to implementing this feature that you already have.
I think this is actually straightforward, and can be done with existing components, adapted for the purpose. Just attach a config button to each project on the dashboard, which would bring up a Docker Desktop-like wizard, or, at a stretch, a Postman-like wizard

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the project dashboard and the existing project-loading flow behind `/projects/load?name=...`; inspect how project actions and URL parameters are currently handled. Define the configuration table or wizard behavior, including how entered parameters affect loading, and consider the Docker Desktop and Postman examples as the requested interaction reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100