I recently set up Directus on my server using the Docker Compose method described in the Docker Guide.
I have also installed a security plugin to check for potential issues with my images. Currently, the Postgis [13-master] and redis:6 versions have been reported as having some security concerns. Would you recommend staying on this version or upgrading to a different one? If upgrading is necessary, what steps can I take to ensure compatibility with the new database version?
Related
Cannot find any information if Jaeger can be executed without docker?
Does a standalone jar exist, or will there be a release in the future for Jaeger like Zipkin has ?
The Downloads page (https://www.jaegertracing.io/download/) lists both the Docker images and the raw binaries built for various platforms (Linux, macOS, windows). You can also build binaries from source.
Just to add to Yuris answer, you can also download the source from github - Github - Jaeger This is useful for diagnosing issues, or just getting a better understanding of how it all works.
I have run both the released apps and custom versions on both windows and linux servers without issues. For windows I would recommend running as a service using Nssm. Nssm details
I want to know what is the difference between installing HortonWorks HDP vs installing the components directly from Apache projects? One thing I can think of is that Horton works probably has the packages aligned so that the version of each component is compatible with that of the others within the suite, while getting them directly from Apache projects, I may have to handle version compatibility myself. Is that correct? Is there any other difference involved ignoring the support subscription aspect of it.
Thanks.
There are a lot of differences between "roll your own" and using a distribution. Some of the most obvious include:
All of the various components and versions have been tested and built to work together - incompatibility between versions (e.g. Hive, Hadoop, Spark, etc.) can be a painful problem to sort through on your own
Most distribution providers, including Hortonworks, will bring patches in from unstable releases into stable releases, so even for the "same" version (e.g. Hive 1.2.1) you're getting a better release than vanilla - these can include both bug fixes and "safe" feature changes
Most distribution providers, including Hortonworks, provide some flavor of centralized platform management. I'm a big fan of Ambari (the one that comes with HDP), for example - it makes configuration and monitoring significantly easier than coordinating a vanilla install
I would strongly recommend against trying to deploy vanilla, unless it's just for learning and playing. HDP community edition is free (both definitions) and a major improvement over doing it yourself. My last deployment of HDP was entirely based on the community edition.
I need to migrate my application to WAS 6.1 to WAS 8.5.5. I would need list of things to be taken care before migration and what are all the major changes involved.
I googled and sufficient informations I couldnt get. Can some one please help me on this ?
One thing to do is to setup an eclipse with IBM WebSphere Application Server Migration Toolkit and then import your application source code (you may even analyse your binaries with Migration Toolkit for Application Binaries) in the workspace.
You then run Software Analyzer and select the Websphere Migration rules.
I am new to Cloudbees and have been trying to find out how I can run an existing Jboss Portal Server based application which we run in our locally hosted CI in Cloudbees infrastructure.
Our stack has the following components
JDK 1.6 JBoss
Portal Server (EPP 4.3)
Oracle Express Edition (XE)
Would appreciate any help from the community to ensure that I dont discard the option of running Jenkins in the cloud on the Cloudbees platform without proper research.
You will have to setup your build job to install and start the adequate runtime
JDK 6 is available as part of CloudBees runtimes, you can then use /private repository to store EPP 4.3 as a zip and expand to /tmp during a pre-build step
Same principle applies to your database, but I'm not sure you can install Oracle XE without user interaction and without being root. I remember doing this myself some years ago on ubuntu and was not as trivial as just unzipping a binary distro.
Is your code tied to this DB ? Or are you using some DB abstraction layer that you could use to test using another DB runtime (mysql / postgres) ?
I want to upgrade Glassfish without internet connection. But I have already downloaded the latest version.
I have done the following steps,
For eg. galssfish-3.0 is the older version and glassfish-3.1 is the newer version.
Step: 1
I just copied the glassfish-3.0/glassfish/domains/domain1 and pasted in glassfish-3.1/glassfish/domains
Step: 2
In glassfish-3.1/bin ./asadmin i just give the command asadmin> start-domain --upgrade
then i checked the version asadmin> version the ouput was
Version = GlassFish Server Open Source Edition 3.1.1 (build 12)
Command version executed successfully.
Is this correct or I need to follow some other ways to achieve this? If wrong Please guide me the right way.
Can anyone help me?
Thanks in advance,
Gnik
Regarding the Oracle GlassFish Server 3.1 Upgrade Guide you did it right.
There are some hints in this guide for the migration of deployed applications:
Application archives (EAR files) and component archives (JAR, WAR, and
RAR files) that are deployed in the source server do not require any
modification to run on Oracle GlassFish Server 3.1. Components that
may have incompatibilities are deployed on GlassFish Server 3.1 with
the compatibility property set to v2 and will run without change on
GlassFish Server 3.1. You may, however, want to consider modifying the
applications to conform to Java EE 6 requirements.
...
Applications and components that are deployed in the source server are
deployed on the target server during the upgrade. Applications that do
not deploy successfully on the target server must be deployed manually
on the target server by the user.
If a domain contains information about a deployed application and the
installed application components do not agree with the configuration
information, the configuration is migrated unchanged, without any
attempt to reconfigure the incorrect configurations.
You should read through the guide carefully and check your deployed applications for any errors / exceptions during server startup or manual redeployment.
Some time ago I made an update as described in the update guide from 3.0 to 3.1.1 and cannot remember any bigger problems.