HN user
@skierkowski http://www.skierkowski.com/
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.
Creating apps that respond to web hooks but are not directly accessible from the internet.
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.
Few more options for "IFTTT for DevOps": http://docs.factor.io/ http://stackstorm.com/ http://www.airstack.io/ https://www.cloudmunch.com/
Factor.io is open-source, there is a hosted version, and self-hosted Pro version.
Those are the open-source docs. The project has been around for well over a year; however, it was open sourced only a couple months ago.
In the mean time you can use https://factor.io/ for "push-to-deploy" with BitBucket or Gitlab.
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.
Something similar: http://staticgen.com/
Same idea, but staticgen.com is a little easier to navigate but don't think it's quite as comprehensive.
Years back I worked on the Azure Service Bus (http://www.windowsazure.com/en-us/develop/net/how-to-guides/...) which has a feature called "Relay". Except in the MS case its way more complicated and .NET-specific. Cool stuff.
Good feedback. We are running A/B tests on some of the contents. Regardless I don't think we answer the basic question "what does Factor.io do?"
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 maciej@factor.io.
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.
I just submitted the first talk proposal called "Docs-driven development". Here is a brief intro: (http://blog.factor.io/post/41716938796/docs-driven-developme...)
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.
I have a love-hate relationship with data. Data is great for helping drive product, messaging, engagement, etc. However, most data ends up as noise. It's noise because it isn't actionable.
Ash Maurya wrote this great article on actionable metrics: http://www.ashmaurya.com/2010/07/3-rules-to-actionable-metri...
In the end I think it depends on how you want to use the data.
Here are a few things that I find useful:
- calculating your ROI on customers by correlating marketing efforts with key metrics. Google Analytics is good for this as you can basically identify the customer origin with a marketing campaign and how they convert for key metrics.
- full funnel perspective and cohort charts for AARRR metrics (http://500hats.typepad.com/500blogs/2007/09/startup-metrics....). KISS Metrics and Mixpanel are great for this, but I still haven't found anything that does the Cohort diagrams that well.
- experimenting with messaging using A/B testing tools like Visual Web Optimizer (http://visualwebsiteoptimizer.com/) which has it's own analytics.
- retention email marketing is great with Customer.io (http://customer.io/) but I have fairly limited experience with that.
Other tools include Statsmix (which I think is under-represented); it is pretty good for collecting custom event data.
Once you have the money for it, tools like Pardot are great for marketing overall. We just implemented this so I still don't have much experience with it personally. It's a full marketing automation tool and has other competitors with higher price tags.
I'd def want to hear more about this.
No. Thanks for the catch.
I'd add one more "focusing on your core".
With PHP it is really easy to hack little things together so it's tempting to build everything yourself when faced with new small challenges. Depending on third party services can save a lot of time/effort to help you deliver what matters.
Gabriel, here are some ideas for you how you measure your idea.
One approach is to list your assumptions (e.g. why does Evernote suck, why would they rather use your app versus writing on paper, they are willing to pay for it, etc). Find customers of your competitors (Evernote, paper-pencil), and validate those assumptions (or reject).
Another method you could try would be to create a landing page on http://unbounce.com/ and start pimping that page and collect email addresses. You can also buy some Google Ads for "Evernote sucks". Once you get those email addresses don't get excited about build an app... that'll just be your initial list of customers to interview.
Cool (free, easy). Where are you going with this?
I wrote an app that does almost the same thing through the UI (not API) http://textfrom.me/ but it's not free. I made that project because I needed to txt a group of folks at a specific time in bulk.
Thanks for the pointer. You should check out Microsoft Windows Azure AppFabric Service Bus (http://www.microsoft.com/windowsazure/AppFabric/Overview/def...). It's supported for .NET by MSFT; however, I think there are other implementations for other platforms. Technologically it is very similar. (I used to be a Program Manager on that team not long ago).
I understand the technology quite well; however, (hope I don't sound rude) I'm not clear on what the value is to the customer (presumably developer) of pagekite.net. Please email me; my email address is on http://www.skierkowski.com/ (I have CAPTCHA on there which is why I don't just give it to you here).
The Amazon Load Balancer only performs load balancing... a reverse proxy can be used for a whole lot of other scenarios... here are just a few...
Rolling Upgrades: you have 20 instances of V1 of your app, you want to slowly test them out, so you start with moving 5 instance to V2, then 5 more, etc. To switch from V1 to V2 gradually to make sure there are no major snags.
Versioning: Make a single API available at the address http://foo.com/V1 and http://foo.com/V2 but those actually go to two different servers running two different applications.
Sub domain to path rewrite: You want to provide customers with sub-domains at <customer>.foo.com but it actually serves up contents from service.foo.com/<customer> on the back-end.
Virtual Sites on single server: Some providers (i.e. some shared services) only allow you to have one or just a few domains/sub-domains for a single instance of your application. Now you can have http://foo.com and http://bar.com actually host up pages from http://foobar.com/ and the original requested address will be in a new HTTP header so your app at http://foobar.com/ can distinguish the two.
Instance Allocation per customer: Some multi-tenant architectures have a "home" node for each customer. In this case you could setup a rule that states that customer a.foo.com goes to instance x while customer b.foo.com goes to instance y.
http://blog.phpfog.com/2011/03/16/scaling-php-up-out-and-aro...
I want to share this article (which I wrote at PHP Fog) about scalability (in PHP but applies to all web apps) and the scenario you are asking about. I agree with travisglines (and everyone else on the thread), that this scenario you are talking about is in fact rare. It's one of those good problems to have. ("I have so much money, how am I going to spend it all")
Most people who I talk to care about scalability, not because they need it now, but rather because they want it as insurance. It sounds like you are in the same boat.
My recommendation is to pick a hosting platform that allows you to build your application the same way you normally would, but allows scalability if you do need it.
Heroku already does this for you for RoR; Windows Azure does this for .NET apps; GAE for Java/Python; and PHP Fog for PHP. Those platforms basically make caching and scalability really easy.
Other than scalability and caching, you should build your application with performance in mind; as having a fast site is important regardless of the number of users. mryan & mooism2 referenced some good resources for doing exactly that.