On Hypernode you can use the installed log-courier to ship your logs to a remote ELK stack. We will be publishing an article some time soon with an example of how to set this up.
app@wifa9a-vdloo-magweb-do:~$ which log-courier
Please specify a configuration file with -config.
The config file to load
Test the configuration specified by -config and exit
write cpu profile to file
On first run, read new files from the beginning instead of the end
List supported transports and codecs
Read from stdin instead of files listed in the config file
show version information
Reopened; seems like the system took over, we never meant to decline!
Hi Ivan, we now run Varnish 4.1.3 backported from Yakkety on the Xenial instances with the official Varnish varnish-modules repository compiled for Hypernode. We only included modules that people actually used on the platform. You can check out our packaging here: https://github.com/ByteInternet/varnish-modules
If you need some other modules than the one currently available please let us know.
Currently we include:
- libvmod-geoip (not in the official bundle because it depends on external libs)
Previously on Precise we also included libvmod-querystring but we noticed that no one used it so we left it out for now until someone requests it. We're deploying this across all nodes later this week.
Hi Ivan, we are currently investigating if we can upgrade to Varnish 4.1 as part of the planned Hypernode Ubuntu Xenial upgrade.
Are there specific features from the VMOD collection you are looking for? Would installing those modules in the current 4.0 installation also solve your problem? I don't think upgrading to Varnish 4.1 is very high on our list of priorities but perhaps we can look into adding some more VMODs.
This will be fixed when we migrate to ubuntu xenial (in progress)
This bug has an extremely low impact. More info can be found here: https://support.hypernode.com/knowledgebase/ssl-errors-in-error-log/
I believe you have been in touch with our engineer Flip regarding this.
Flip created a snippet of code which in my understanding does exactly what you want.
It will fetch the production urls and set the equivalent staging urls in the /data/web/staging magento1 installation.
Use at your own risk!
The snippet is here:
https://gist.github.com/hn-support/d7a6fdd89bd78ebd7a03982605743616 (for m2)
https://gist.github.com/hn-support/faf03c5898f5553b7fd9f4059709aef4 (for m1)
If this feature request gets many votes we may improve this script (if needed) and ship it on all hypernodes.
Let us know how it goes!
Hi Michel, you can currently achieve something like this using the shop importer tool in the control panel and a second Hypernode (we now have Hypernode Development plans which are great for this). You can run the shop importer to import a shop from one Hypernode to another Hypernode with one click after filling in the SSH credentials of the production Hypernode. Then you can use the copied shop as a staging environment. You can find the importer tool (the Webshop importeren button) in the control panel under the 'Instellingen' tab.
We currently don't offer IPv6 yet. As a workaround, you can use cloudflare untill IPv6 become's available on hypernodes.
If you voted for this feature, could you leave a comment and describe your use case?
We've added Sphinx Search to Hypernode Go Big. http://hypernode.uservoice.com/forums/242854-hypernode/suggestions/6789502-sphinx-deamon. Can you work with that? Please let us know in the comment field!
Listing should be easy. Creating, upgrading, deleting however is more of a problem, because it enters into the realm of contracts and payments and such.
I imagine you would use the listing most often, to integrate your systems. What fields would you like to see in the API?
Also, please login so we can contact you out-of-band :)
Have you seen this documentation page?
This has solved this problem before.