Would be great to have some transparency, perhaps a "# of users banned in this repo". That'd be one way to see where the balance of "abuse" lies, with the repo/org or the contributors. In other words, another indicator for health of the community, just like # of stars, forks, contributors, and watchers.
"fastlane lets you define and run your deployment pipelines for different environments. It helps you unify your app’s release process and automate the whole process. fastlane connects all fastlane tools and third party tools, like CocoaPods and Gradle." directly from the horses mouth https://fastlane.tools/
I'm obviously a fan.
It's a Ruby-based DSL that wraps a collection of small CLI tools to define the entire workflow. It can handle most aspects out-of-box like building, signing, taking a snapshot, pushing, etc. It appears to be extensible too, but I haven't tried that much yet.
We fixed the XSS issue. Having said that, this site is just to demonstrate that you can use any standard web socket client (including the one in your browser); normally you would build the XSS mitigation into the client app if necessary.
What scenario do you have in mind for a "pub-sub pattern using WS"?
It might not be the scenario we were shooting for. The HTTP endpoint was an important requirement. We needed a way to receive HTTP POST calls in an app which wasn't accessible from the web (i.e. no incoming HTTP, but we could make an outbound WS call). Something like Runscope's Passageway (https://www.runscope.com/docs/passageway) would have been our first choice, but it wasn't easy to bake it into the app itself.
Would love to see the API support a POST for creating a new build and passing in the project code (or slug url). This would enable the other git providers (Gitlab, BitBucket, Gogs, etc) and 3rd party services/frameworks (e.g. Factor.io) to provide the integration.
I can't speak for others, but I can for Factor.io’s twist... (1) It is Open Source + Hosted + Pro. (2) The recipes ("workflows") can include multiple steps, sequential, and parallel activities; not just limited to if-this-then-that. (3) Workflows are defined programmatically using a Ruby-DSL. (4) You can create both actions and listeners (like events/monitors), though some of the others support this too. (5) It's been around for 2+ years, built with feedback from 100+ dev teams, and used by 1000s.
Have a look at https://factor.io, it is also a deployment engine which can deploy from Github, Bitbucket, etc to your servers (e.g. SCP). It's also much easier to setup. Additionally you can add an intermediate build step with static gen frameworks like Middleman.
Factor.io might be a good fit for you. I am the co-founder/CEO and I hate self promoting, but in this case I think that we can help. We provide a way for you to create workflows like the one you described. It's kind of like IFTTT/Zapier for Dev/DevOps. But we support running numerous actions, custom code for new extensions, and more complex operations. Still in private beta, but would love to help out and get you to test it out. Shoot me an email [email protected].
Back in the day (~4 yrs ago) there was a project called "Casablanca" at Microsoft which was supposed to be the native (C/C++) version of the Windows Communication Foundation. Is this the same "Casablanca"?
Pricing hasn't yet been announced, but a draft is in progress, I'd love your feedback. Here is what we are thinking.
Free for all public-cloud services.
Paid if you want to run the workflows on your own servers. For example, you could run a workflow which includes a step like "run shell command xyz" which could execute on your own servers. This paid plan would start at $100/month for 4 servers.
Also planning an enterprise plan which doesn't limit the number of servers and also includes premium support and implementation support, which starts at $5,000/month.
Yeah. By "OS" i mean "open-source" not "iOS". I was thinking it'd be a web app where you can manage multiple lists each one with categories and items. When you are ready to release you just select the repo and milestone from Github and it creates issues for each of the checkbox items.
Is it time for feature requests? It'd be great to get integration with common management tools (e.g. Github Issues, Trello), so that the list can automatically be imported for a given milestone.
One thing that's cool about KISS metrics is that they have an export feature which actually exports all your data to S3 buckets on a daily basis. Great for those that are worried about data retention.