I'm still struggling to get it fully working, and in particular, to understand how processes are launched, such as psql.
I have a repo containing the frontend(expo) and the backend(rails), and I use rspec to test my frontend code, which is run against a another process serving the frontend(a simple nodejs on another port, and I change Capybara.app_host).
Ideally, I would have be able to:
setup and build my rails app(as described)
setup and build my frontend app
run a the lightweight server to serve my front end
run rspec (with the other server running, to be able to load the html)
Wondering how/if this can be accomplished with github actions though!
Backend Engineer @Toptal(Core Team). Experienced in Ruby on Rails, NodeJS and VueJS web application development. Working in the industry for more than 9 years now.
I have never done that. Will be nice though. Github actions is like docker try searching for some node official action and run it after ruby action is complete.
Backend Engineer @Toptal(Core Team). Experienced in Ruby on Rails, NodeJS and VueJS web application development. Working in the industry for more than 9 years now.
Great post, and great explanations!
I'm still struggling to get it fully working, and in particular, to understand how processes are launched, such as psql.
I have a repo containing the frontend(expo) and the backend(rails), and I use rspec to test my frontend code, which is run against a another process serving the frontend(a simple nodejs on another port, and I change
Capybara.app_host).Ideally, I would have be able to:
Wondering how/if this can be accomplished with github actions though!
I have never done that. Will be nice though. Github actions is like docker try searching for some node official action and run it after ruby action is complete.
that's what i'm on, but i guess the process is killed before the ruby action runs..
You can call another action in one action that might help your cause.
will keep you posted and share the solution!