Skip to content
New issue

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

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

Already on GitHub? # to your account

FireEdge Sunstone as main WebUI #97

Open
3 tasks
dgarcia18 opened this issue Nov 7, 2024 · 0 comments
Open
3 tasks

FireEdge Sunstone as main WebUI #97

dgarcia18 opened this issue Nov 7, 2024 · 0 comments

Comments

@dgarcia18
Copy link

Description
Not a bug but a suggestion for future versions. Since RSunstone will be soon deprecated, FSunstone should be configured as the main WebUI in the Apache config.

To Reproduce
Provision an OpenNebula cloud with Apache2 enabled.

Expected behavior
FireEdge Sunstone should be reachable as the default WebUI (In the / route). The following Apache config is suggested for non-SSL deployments:

<VirtualHost *:80>
  ServerName <OMITTED>

  PassengerUser oneadmin

  # Remove or comment out the GEM_PATH and GEM_HOME lines if they are no longer needed for Sunstone:
  # SetEnv GEM_PATH /usr/share/one/gems/
  # SetEnv GEM_HOME /usr/share/one/gems/


  # Proxy configuration to route / to localhost:2616
  ProxyRequests     off
  ProxyPreserveHost on

  # Forward the root path / to localhost:2616
  ProxyPass        / http://localhost:2616/
  ProxyPassReverse / http://localhost:2616/

  # WebSocket upgrade rules
  RewriteEngine on
  RewriteCond %{HTTP:Upgrade} websocket [NC]
  RewriteCond %{HTTP:Connection} upgrade [NC]
  RewriteRule ^/?(.*) "ws://localhost:2616/$1" [P,L]

  <Location />
      Order deny,allow
      Allow from all
  </Location>
</VirtualHost>

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant