Public facing websites need to have some basic search engine optimization (SEO) tags, such as <title> and <meta name="description">. In Rails, you could achieve this pretty simply by putting a yield :head tag in the appropriate layout.
We recently finished up a large Phoenix project at Infinite Red, and we learned some tips and tricks along the way that I want to share. Overall, we’ve been impressed at how well organized and maintainable a Phoenix project can be beyond 10,000 lines of code. Some of the tips in this post are specific to Phoenix, others could be equally applied to Rails or other web frameworks. None of them are me
September 27, 2016 We all have logic in our applications like this: When a user is created, send a notification to an admin When a post is deleted, remove it from the search cache When a password is reset, log out that user’s active sessions These side effects need to be predictable and reliable. Often, they’re some of the key business logic of the whole application. Many Rails applications store
Christian, husband, father, and programmer. I write code for the web. In my spare time, I’ve been working on a little Phoenix project that involves a JSON API. Developers frequently neglect rate limiting when they build an API, assuming they are even aware that it is a best practice. It’s true that in many cases rate limiting isn’t worth the effort, but when it comes to authentication, it definite
I recently started working on a Phoenix project at Infinite Red that uses Elasticsearch to power a search feature. In our development environments, we needed a good way to ensure that Elasticsearch was running whenever Phoenix was running. Obviously, there are a lot of ways we could do this. We could, for example, have everyone install Elasticsearch through Homebrew with “brew install elasticsearc
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く