Phoenix
act
Our great sponsors
Phoenix | act | |
---|---|---|
111 | 145 | |
20,558 | 49,985 | |
0.8% | 3.2% | |
9.4 | 9.2 | |
6 days ago | 5 days ago | |
Elixir | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Phoenix
-
Idempotent seeds in Elixir
A standard Phoenix app contains a priv/repo/seeds.exs script file, which populates a database when it is run, so that developers can work with a conveniently prepared environment.
-
Ask HN: Did you encounter any Leap Year bugs today? How bad was it?
There was one in the Phoenix Framework (Elixir) about issuing certificates with an invalid end date: https://github.com/phoenixframework/phoenix/issues/5737
Interestingly, Azure had this bug some years ago too leading to an outage. https://azure.microsoft.com/en-us/blog/summary-of-windows-az...
-
Aplicando MVVM en Phoenix LiveView
Official website: https://www.phoenixframework.org/
-
Things I like about Gleam's Syntax
Since you mention Rails, have you seen https://www.phoenixframework.org/
-
Building Apps with Tauri and Elixir
Thus, we set out to build a desktop application using a LiveView from the Phoenix Framework in Elixir. For the uninitiated, a LiveView is a process that receives events, updates its state, and renders updates to a page as diffs. The LiveView programming model is declarative: instead of saying “once event X happens, change Y on the page”, events in LiveView are regular messages which may cause changes to its state.
-
Has anybody compared Phoenix Framwork vs. Blazor?
It seems though like Phoenix is similar like Blazor Server (using web socket), but Phoenix is: SEO friendly (first render is plain html) Light weight, scales well and concurrency is first class Easy to develop (runs a local server so you see live updates) Compiled With auth out of the box https://www.phoenixframework.org/
-
Ask HN: Why isn't Phoenix/Elixir more mainstream?
Sorry to hear this. Phoenix v1.7 changed how it structures files in disk and that broke quite some of the getting started material. However, the guides are always kept up to date, so you can give it a try: https://hexdocs.pm/phoenix/overview.html
You can also see the resources on this page listed by year: https://github.com/phoenixframework/phoenix/blob/main/guides... - the recent launched ones are most likely up to date.
-
Emoji Generator with AI
Yes! I love Elixir :) [Phoenix LiveView](https://www.phoenixframework.org/) is really amazing. I feel so fast working in it. I got hooked after watching Chris McCord's ['Build a real-time Twitter clone in 15 minutes'](https://www.youtube.com/watch?v=MZvmYaFkNJI&embeds_referring...), and things have improved a lot since then.
-
Ask HN: What's the best modern back end?
I still work on a lot of Java projects. As of JDK 17 Java has most of "ML the good parts" and has the same scalable, reliable and high-performance threading Java is famous for. JAX-RS provides a Sinatra style framework that makes it easy to write JSON API back ends. JDK 21 is just about to come out as a long term supported version and it will be even better.
I do my side projects in Python with aiohttp and think it is a lot of fun even though people tell me it is suicide (I guess if you block the thread you are in trouble)
I think "Next.js" really wants a node.js backend which has the big advantage that you can share code with the front end and back end. It's basically single-threaded but I know people who are happy with it.
The system I'd most like to try is
https://www.phoenixframework.org/
which is just great if you want to do stuff with websockets that is more interactive than what most people are doing.
- Ask HN: Leetcode for Back End and Server Development
act
-
How to debug GitHub actions. Real-world example
When it comes to the alternatives to tmate, there is another great debugging tool that you could check out. It is called act and it allows you to run GitHub Actions code on your local machine making debugging even easier. It has its own limitations and some learning curve but overall it is another tool you should use if you can’t fix the CI bugs by connecting directly into the running action with the tmate.
-
Using my new Raspberry Pi to run an existing GitHub Action
Link: https://github.com/nektos/act
-
Show HN: Open-source x64 and Arm GitHub runners. Reduces GitHub Actions bill 10x
Could you upload your build of GitHub's runner image to Docker Hub?
This would be quite useful for users of other GitHub Actions clones like act [0].
[0]: https://github.com/nektos/act
-
Git commit messages are useless
> These kinds of commit messages are typically an indicator of a broken process where somebody needs to commit to see something happen, like a deployment or build process, and aren't able to assert that stuff works locally.
This is one of my biggest pet peeves with services like github actions. Something running locally like "act" [1] isn't sufficient because it doesn't have everything github has and is extra friction anyway to get everyone to use it for testing.
[1] https://github.com/nektos/act
-
Essential Command Line Tools for Developers
View on GitHub
-
What’s with DevOps engineers using `make` of all things?
If you use Github actions, act is incredibly useful. It can be used to test your GH actions, but also serves as an interface for running tasks locally.
-
Streamlining CI/CD Pipelines with Code: A Developer's Guide
That's something that often is difficult or basically impossible. Except for maybe GitHub actions through Act (https://github.com/nektos/act). I'd still lean to something in the yaml sphere if it eventually would be used in deployment pipelines and such. For example a solution incorporating ansible.
It also seems to me that the argument you make is mostly focused on the building step? Earthly certainly seems focused on that aspect.
-
GitHub Actions Are a Problem
I feel I'm being trolled, but I'll bite and accept the resulting downvotes
I don't think treating every mention of act as an opportunity for airing of personal grievances is helpful in a discussion when there's already ample reports of people's concrete issues with it, had one looked at the 800 issues in its repo https://github.com/nektos/act/issues?q=is%3Aissue or the 239 from gitea's for https://gitea.com/gitea/act_runner/issues or whatever is going on with Forgejo's fork https://code.forgejo.org/forgejo/act .
But, as for me specifically, there are two and a half answers: I wanted to run VSCodium's build locally, which act for sure puked about. Then, while trying to troubleshoot that, I thought I'd try something simpler and have it run the lint job from act's own repo <https://github.com/nektos/act/blob/1252e551b8672b1e16dc8835d...> to rule out "you're holding it wrong" type junk. It died with
[checks/lint] Failure - Main actions/setup-go@v3
-
How Steve Jobs Saved Apple with the Online Apple Store
https://twitter.com/mitsuhiko/status/1720410479141487099 :
> GitHub Actions currently charges $0.16 per minute* for the macOS M1 Runners. That comes out to $84,096 for 1 machine year*
GitHub Runner is written in Go; it fetches tasks from GitHub Actions and posts the results back to the Pull Request that spawned the build.
nektos/act is how Gitea Actions builds GitHub Actions workflow YAML build definition documents. https://github.com/nektos/act
https://twitter.com/MatthewCroughan/status/17200423527675700... :
> This is the macOS Ventura installer running in 30 VMs, in 30 #nix derivations at once. It gets the installer from Apple, automates the installation using Tesseract OCR and TCL Expect scripts. This is to test the repeatability. A single function call `makeDarwinImage`.
With a Multi-Stage Dockerfile/Containerfild, you can have a dev environment like xcode or gcc+make in the first stage that builds the package, and then the second stage the package is installed and tested, and then the package is signed and published to a package repo / app store / OCI container image repository.
SLSA now specifies builders for signing things correctly in CI builds with keys in RAM on the build workers.
"Build your own SLSA 3+ provenance builder on GitHub Actions" https://slsa.dev/blog/2023/08/bring-your-own-builder-github
- Overview
What are some alternatives?
Django - The Web framework for perfectionists with deadlines.
reverse-rdp-windows-github-actions - Reverse Remote Desktop into Windows on GitHub Actions for Debugging and/or Job Introspection [GET https://api.github.com/repos/nelsonjchen/reverse-rdp-windows-github-actions: 403 - Repository access blocked]
sugar - Modular web framework for Elixir
cache - Cache dependencies and build outputs in GitHub Actions
hotwire-rails - Use Hotwire in your Ruby on Rails app
dagger - Application Delivery as Code that Runs Anywhere
kitto - Kitto is a framework for interactive dashboards written in Elixir
earthly - Super simple build framework with fast, repeatable builds and an instantly familiar syntax – like Dockerfile and Makefile had a baby.
trot - An Elixir web micro-framework.
action-tmate - Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.
RIG - Create low-latency, interactive user experiences for stateless microservices.
LSPatch - LSPatch: A non-root Xposed framework extending from LSPosed