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

Ioan Eugen Stan commented on JAMES-3217:
----------------------------------------

Yes, it's always a hard decision - what to include by default and what not to. 

The way I see it, the purpose of 
https://github.com/ieugen/james-self-hosting-sandbox is to serve as a template 
for Build Your Own James Email Server (BYOJES (trademark pending :D ) ) . 

I'll pair this with [git-repository-templates] to make it easy for people to 
have a quick start for their own version of Apache James:
- sample code
- ways of adding dependencies
- sample configurations

We could have a few templates:
- James for Small and Medium Business (James for SMB) - the one that I will be 
focusing on with [~dleangen] - How would a small business host their own email 
services. This should be easy to setup and with very few dependencies. 
- James for email hosting providers - template for a distribution of James 
focusing on large scale deployments
- Other specialized use cases: ???!?!? 

[git-repository-templates] 
https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-template-repository
https://docs.gitlab.com/ee/user/admin_area/custom_project_templates.html 


> Describe how to include dependencies for the James Local Server
> ---------------------------------------------------------------
>
>                 Key: JAMES-3217
>                 URL: https://issues.apache.org/jira/browse/JAMES-3217
>             Project: James Server
>          Issue Type: Sub-task
>            Reporter: David Leangen
>            Priority: Major
>
> A working server requires the correct dependencies.
> It should be easy for users to gather the right dependencies to set up the 
> James Local Server.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to