Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[analysis] container initialization with data (init payload) in dapps #72

Open
1 task
VanDavv opened this issue Dec 7, 2022 · 3 comments
Open
1 task

Comments

@VanDavv
Copy link

VanDavv commented Dec 7, 2022

During the application development, there are cases when an image prepared once can be used for different purposes by just giving it a different initial payload.

For example, having an NGINX image, the internal configuration and installed applications can stay the same, whereas the HTML files to be served can be uploaded during the initialization stage.

With this task, we should make sure we have an initialization mechanism, where users can provide an initial payload that will be sent to the app image.

Todo:

  • Prepare design doc for new "transfer" command for descriptor, based on ExecScript.TRANSSFER
@shadeofblue
Copy link
Contributor

Well, this one should probably go through a GAP process first before we start the implementation

@VanDavv
Copy link
Author

VanDavv commented Jan 30, 2023

@stranger80 do we have this included in any GAP already?

@stranger80
Copy link
Contributor

We spoke about this a while ago. GAOM descriptor does include service.init attribute which specifies the ExeScript sequence to execute when launching a service. This ExeScript may include TRANSFER statements to upload arbitrary content to the runtime, for the payload to use.

@approxit approxit changed the title Implement container initialization with data (init payload) in dapps [analysis] container initialization with data (init payload) in dapps Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants