Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore whether to have a headless option for advanced tech stacks - added [done] #240

Closed
kensoh opened this issue Apr 25, 2021 · 4 comments
Labels

Comments

@kensoh
Copy link
Member

kensoh commented Apr 25, 2021

eg building an implementation on Docker for Linux without displays / Xvbf

source - Allan

@kensoh kensoh added the feature label Apr 25, 2021
@kensoh kensoh changed the title Explore whether to have a headless option - for advanced tech stacks Apr 25, 2021
kensoh added a commit that referenced this issue May 12, 2021
@kensoh
Copy link
Member Author

kensoh commented May 12, 2021

This is added in v1.34, available with pip install rpa --upgrade

Note that many websites are not designed to work properly in headless mode.

  • Headless mode can be activated with r.init(headless_mode = True)
  • Use r.snap('page', 'browser.png') to take a snapshot for troubleshooting
  • For debugging, I recommend using Jupyter Notebook or Python interactive mode
@kensoh kensoh changed the title Explore whether to have a headless option for advanced tech stacks - to explore May 12, 2021
@kensoh kensoh changed the title Explore whether to have a headless option for advanced tech stacks [done] May 12, 2021
kensoh added a commit that referenced this issue May 12, 2021
@skadefro
Copy link

Thank you.

@lanSeFangZhou
Copy link

can rpa deploy online like a service?

@kensoh
Copy link
Member Author

kensoh commented Jun 28, 2022

The package definitely can be run on the cloud on Linux servers. See this working example of running on Google cloud via Google Colab, which users can create their workflows and run on their desktop or phone web browsers - https://colab.research.google.com/drive/13bQO6G_hzE1teX35a3NZ4T5K-ICFFdB5?usp=sharing

However, the package is primarily designed to run locally on a user computer. Thus if you run on the cloud, you will have to design and create your own API endpoints, as well as handle issues with queues or concurrency, since you may get multiple requests before an existing automation has completed running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 participants