activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-390) Linux folder structure
Date Mon, 15 Feb 2016 00:38:18 GMT

    [ https://issues.apache.org/jira/browse/APLO-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146805#comment-15146805
] 

clebert suconic commented on APLO-390:
--------------------------------------

Artemis is following the same pattern, and I don't see the issue TBH.


You could have multiple servers... and having everything spread at /etc, /usr/local could
cause you issues of isolation. it would be hard to manage multiple servers. (think of dev
time versus production time, backups.. etc)

> Linux folder structure
> ----------------------
>
>                 Key: APLO-390
>                 URL: https://issues.apache.org/jira/browse/APLO-390
>             Project: ActiveMQ Apollo
>          Issue Type: New Feature
>    Affects Versions: need-info
>         Environment: Linux
>            Reporter: Mustafa Talaeezadeh Khouzani
>            Priority: Minor
>
> The Apollo folder structure is roughly based on linux system structure but centralized
in one main directory. It is more convenient for linux users to first have a package (apt,
rpm, etc.) to install and basic setup. 
> Secondly, have a similar structure eg. the etc folder would be placed as /etc/apollo
and bin is located in /usr[/local]/bin and lib is placed under /usr/lib[64]/apollo by default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message