Replies: 1 comment
-
Maybe if you add the sea-config.json to itself, you can then parse it as json, and get the list of assets. Meets the "define once " test, and relatively low overhead at runtime |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to write an SEA that will let my users easily deploy projects to a hosted server.
Right now almost everything is working great! I can run
mySEAApp <path_to_some_foler_to_deploy>
and it parses through all the files in the directory provided, updates the things it needs to update (ie injects some headers into specific files), and pushes it all to my remote server.The next thing I need to do is add a few standard files to the folder before its deployed it to the remote server. I think the right way to do this is by adding those files as assets to my
sea-config.json
file. I'm assuming I could individually specify each of these and copy them over, but I'm wondering if there is any way to get a list of the assets I specified in the config from the SEA just so I don't have to manually code each of them.Right now I'm assuming I have to do something kind of like this...
I'm hoping I can do this, so I don't have to update the code any time I add a new asset to the config.
Beta Was this translation helpful? Give feedback.
All reactions