All Projects → apache → activemq-website

apache / activemq-website

Licence: other
Apache ActiveMQ Website

Programming Languages

HTML
75241 projects
javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to activemq-website

activemq-nms-api
Mirror of Apache ActiveMQ NMS API
Stars: ✭ 30 (+87.5%)
Mutual labels:  activemq, network-server, network-client
activemq-nms-amqp
Mirror of Apache ActiveMQ NMS.AMQP Client
Stars: ✭ 37 (+131.25%)
Mutual labels:  activemq, network-server, network-client
Activemq
Mirror of Apache ActiveMQ
Stars: ✭ 1,970 (+12212.5%)
Mutual labels:  activemq, network-server, network-client
couchdb-couch-plugins
Mirror of Apache CouchDB
Stars: ✭ 14 (-12.5%)
Mutual labels:  network-server, network-client
synapse
Apache Synapse is a lightweight and high-performance Enterprise Service Bus (ESB)
Stars: ✭ 43 (+168.75%)
Mutual labels:  network-server, network-client
couchdb-mango
Mirror of Apache CouchDB Mango
Stars: ✭ 34 (+112.5%)
Mutual labels:  network-server, network-client
qpid-cpp
Mirror of Apache Qpid C++
Stars: ✭ 77 (+381.25%)
Mutual labels:  network-server, network-client
guacamole-manual
Mirror of Apache Guacamole Manual
Stars: ✭ 23 (+43.75%)
Mutual labels:  network-server, network-client
Couchdb
Seamless multi-master syncing database with an intuitive HTTP/JSON API, designed for reliability
Stars: ✭ 5,166 (+32187.5%)
Mutual labels:  network-server, network-client
Thrift
Apache Thrift
Stars: ✭ 8,821 (+55031.25%)
Mutual labels:  network-server, network-client
Guacamole Server
Mirror of Apache Guacamole Server
Stars: ✭ 1,931 (+11968.75%)
Mutual labels:  network-server, network-client
Ignite
Apache Ignite
Stars: ✭ 4,027 (+25068.75%)
Mutual labels:  network-server, network-client
couchdb-pkg
Apache CouchDB Packaging support files
Stars: ✭ 24 (+50%)
Mutual labels:  network-server, network-client
Activemq
activeMQ消息封装,主要解决:事务性消息、消息幂等性、异常造成的消息丢失问题 本项目不在更新,新项目请看ReliableMessageSystem: 本项目不再更新,新的版本迁移至ReliableMessageSystem 详情请看:https://github.com/zjpjohn/ReliableMeageSystem
Stars: ✭ 124 (+675%)
Mutual labels:  activemq
tomcat-native
Mirror of Apache Tomcat Native
Stars: ✭ 73 (+356.25%)
Mutual labels:  network-server
Dubbo2.5 Spring4 Mybastis3.2 Springmvc4 Mongodb Redis
dubbo2.5-spring4-mybastis3.2-springmvc4-mongodb-redis整合
Stars: ✭ 123 (+668.75%)
Mutual labels:  activemq
Jmstoolbox
Free universal JMS client
Stars: ✭ 119 (+643.75%)
Mutual labels:  activemq
Thunder
⚡️ Nepxion Thunder is a distribution RPC framework based on Netty + Hessian + Kafka + ActiveMQ + Tibco + Zookeeper + Redis + Spring Web MVC + Spring Boot + Docker 多协议、多组件、多序列化的分布式RPC调用框架
Stars: ✭ 204 (+1175%)
Mutual labels:  activemq
A
ActiveMQ CLI testing and message management
Stars: ✭ 116 (+625%)
Mutual labels:  activemq
Myth
Reliable messages resolve distributed transactions
Stars: ✭ 1,470 (+9087.5%)
Mutual labels:  activemq

Apache ActiveMQ Website

This is the repository for the Apache ActiveMQ website, hosted at activemq.apache.org.

How it works

This branch of the repo contains the source files that are used to generate the HTML that ultimately gets pushed to the site. When a commit is made to the branch, a Jekyll build is automatically performed in CI and the generated site output committed back to the asf-site branch within the output directory. The generated content on asf-site is then automatically published to the live web server at https://activemq.apache.org/.

See the Contributing section below for more.

To Build the site locally

The site is built using Jekyll. Before building the site you will need to install a Ruby development environment, and GCC. The Jekyll site has guides that may help get you started with these pre-requisites.

You need to install the Bundler tool with:

gem install bundler

Then ensure you are within a checkout directory of the website repo for instructions/commands that follow.

You can optionally isolate the ActiveMQ website dependencies from your general environment by configuring Bundler to use a local install path with bundle config set path --local vendor/bundle from within the site checkout. This sets the ./.bundle/config file to have Bundle install items in the ./vendor/bundle directory. Both are ignored in .gitignore to help prevent showing or checking in changes to them.

You can then use Bundler to install the required dependencies:

bundle install

You can now build (from the src directory, to the _site output directory) and serve + reload the site locally using Jekyll to test changes as you make them:

bundle exec jekyll serve --livereload

You can view the site by navigating to the printed Sever Address, e.g http://127.0.0.1:4000.

Alternatively, rather than serving the site, to just build the site simply run:

bundle exec jekyll build

Helper scripts ./serve.sh and ./build.sh are provided which do an inline bundle install followed by jekyll serve or build.

If for some reason you need to clear the metadata/cache used to support the build process, and the build output, you can run:

rm -rf src/.jekyll-*
rm -rf _site

There is a ./clean.sh helper script provided that does the above.

Note there is also a ./serve_subset.sh helper script. This uses additional configuration from _config_subset_excludes.yml to omit building larger content like javadocs and older release content that doesnt typically change, significantly improving responsiveness while working on additions not affecting those areas. It works best when starting without existing full _site output, which can be cleaned out as noted above.

Contributing to the site

If you would like to make a change to the ActiveMQ site:

  1. Fork the Apache ActiveMQ site repository to your github account.
  2. Create a new branch from main
  3. Test your changes locally
  4. Add commit(s) to your branch
  5. Open a pull request on the github mirror
  6. An ActiveMQ committer will review and merge your changes

If you are a committer, do the following:

  1. Clone https://gitbox.apache.org/repos/asf/activemq-website.git.
  2. Update the main branch with your (or a Pull Request's) changes.
  3. Run serve.sh or build.shand verify the updates look appropriate.
  4. Push the changes to the ASF remote.
  5. The CI build will run and commit the generated site to the asf-site branch automatically within a few minutes, from where it will also be published. CI build status mails go to the commits list.
  6. Verify the updated website works as expected by browsing it.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].