Sebastian,
so you are talking about an all-in-one-amber.js which is minimized, an
issue we had before and where we still have problems....?
Last year I worked with r.js to string everything together and it
worked at a certain point of time with a certain version of amber.
You mentioned repeatedly that you did a manual concat of all the amber
files and it worked quite well. Is it possible to automate this?
I have been working on this Amber project for a while. It's my first Single Page App (wow - there is a learning curve there), and I'm still finishing up some work on it. Over the weekend (probably Sunday) - I'll post more about my deployment process and the project in general.
JohnnyT
On Friday, May 2, 2014 8:26:27 AM UTC-6, Sebastian Sastre wrote:
On May 2, 2014, at 11:15 AM, H. Hirzel <hannes...@gmail.com> wrote:Sebastian,
so you are talking about an all-in-one-amber.js which is minimized, an
issue we had before and where we still have problems....?
Last year I worked with r.js to string everything together and it
worked at a certain point of time with a certain version of amber.
You mentioned repeatedly that you did a manual concat of all the amber
files and it worked quite well. Is it possible to automate this?
Good question. That’s the best idea I have so far but my point here is try to capitalize on good experiences that other amberians I assume are having..deploy.js isn’t there anymore in this version so I’d love to hear what others have to sayWhat you guys are doing for that goal?Are you using closure compiler on the concatenated .js files? or something else? any advice evading a known pitfall?Com on guys... this is not time to be shy, this is time to deliver real value with thisDon’t let me down, what’s your pro advice?
Sebastian Sastre <sebastia...@gmail.com>napísal/a:
Get it.
Can we write the to-do list of the ideal steps we need to get it done?
What would you now if you have developed the app and you need to deploy this afternoon?
Writing into your form:
1. commit the package from Helios/legacy
2. `amber config deploy`
3. `node .../r.js -o allinone.js amber.config.js`, or
3. `amber pack -o allinone.js`
4a. `git push`
4b. CI / CD gets involved
4c. Run tests
5. upload to server
6. profit
Of course, 4a and 4b can go further up and actually automate everything since 2.
I don't know if 3. is needed to build into amber, for flexibility it would just delegate to r.js (adding amber.config.js), but `amber init` precedent shows people rather use prepackaged command then use the building blocks directly as learning curve is then less steep.
Herby
I have been working on this Amber project for a while. It's my first Single Page App (wow - there is a learning curve there), and I'm still finishing up some work on it. Over the weekend (probably Sunday) - I'll post more about my deployment process and the project in general.