5 ms·
I'm not going to stop hacking around this mess until this mess is open source. It's a personal preference, but at that point I'll be willing to pitch in and sta
by traverseda 8y ago
I'm not going to stop hacking around this mess until this mess is open source. It's a personal preference, but at that point I'll be willing to pitch in and start fixing this mess.
- scarface74 8y agoWhat do you need to be open source? Using Codebuild, you just put a buildspec.yml file in the root directory of your source directory containing a few import statements, and a list of wildcard file specifications to tell CodeBuild what to include in your zip file artifact. It's not like there is a lot of "vendor lock in" for a 10 line yml file.
- traverseda 8y ago>It also doesn't help that there's a lack of information or simply misinformation out there. Sometimes I think frameworks with a very specific use-case like Zappa do more harm than good. Yes, it's easier to get running, but it doesn't give you a general purpose solution and makes you think everyone is just hacking around the mess. I'm generally unwilling to learn skills that only apply to a proprietary environment. If aws was using openwhisk, I'd probably code directly against that instead of using a hack like zappa.
- scarface74 8y agoI didn’t suggest Zappa. Zappa is not the AWS solution. The AWS Solution is using CodeBuild. With CodeBuild you would just specify the bash commands you want to run to create your zip file with a yml file. But you’re already talking about using lambda so you’re already using something proprietary. On a deeper level, if you work for a company, you’re probably learning a lot of business specific stuff anyway that’s not transferable.