Merge remote-tracking branch 'origin/main'
This commit is contained in:
Nevo David
commit
0f2ac5f28d
|
|
@ -4,8 +4,16 @@ eg: Bug fix, feature, docs update, ...
|
|||
|
||||
# Why was this change needed?
|
||||
|
||||
Please link to related issues when possible.
|
||||
Please link to related issues when possible, and explain WHY you changed things, not WHAT you changed.
|
||||
|
||||
# Other information:
|
||||
|
||||
eg: Did you discuss this change with anybody before working on it (not required, but can be a good idea for bigger changes). Any plans for the future, etc?
|
||||
eg: Did you discuss this change with anybody before working on it (not required, but can be a good idea for bigger changes). Any plans for the future, etc?
|
||||
|
||||
# Checklist:
|
||||
|
||||
Put a "X" in the boxes below to indicate you have followed the checklist;
|
||||
|
||||
- [ ] I have read the [CONTRIBUTING](CONTRIBUTING.md) guide.
|
||||
- [ ] I checked that there were not similar issues or PRs already open for this.
|
||||
- [ ] This PR fixes just ONE issue (do not include multiple issues or types of change in the same PR) For example, don't try and fix a UI issue and include new dependencies in the same PR.
|
||||
|
|
|
|||
|
|
@ -14,20 +14,41 @@ As a general rule;
|
|||
- **If a change is less than 3 lines**: You're probably safe just to submit the change without a discussion. This includes typos, dependency changes, and quick fixes, etc.
|
||||
- **If a change is more than 3 lines**: It's probably best to discuss the change in an issue or on discord first. This is simply because you might not be aware of the roadmap for the project, or understand the impact this change might have. We're just trying to save you time here, and importantly, avoid you being disappointed if your change isn't accepted.
|
||||
|
||||
## Types of Contributions
|
||||
|
||||
Contributions can include:
|
||||
- **Code improvements:** Fixing bugs or adding new features.
|
||||
- **Documentation updates:** Enhancing clarity or adding missing information.
|
||||
- **Feature requests:** Suggesting new capabilities or integrations.
|
||||
- **Bug reports:** Identifying and reporting issues.
|
||||
|
||||
## How to contribute
|
||||
|
||||
This project follows a Fork/Feature Branch/Pull Request model. If you're not familiar with this, here's how it works:
|
||||
|
||||
1. Fork the project to your GitHub account.
|
||||
2. Clone your fork to your local machine.
|
||||
3. Create a new branch for your changes.
|
||||
4. Make your changes in this new branch.
|
||||
5. Push your changes to your fork.
|
||||
6. Create a pull request from your fork to this project.
|
||||
7. We'll review your changes and approve or comment on them.
|
||||
1. **Fork the project:** Create a personal copy of the repository on your GitHub account.
|
||||
2. **Clone your fork:** Bring a copy of your fork to your local machine.
|
||||
```bash
|
||||
git clone https://github.com/YOUR_USERNAME/postiz.git
|
||||
```
|
||||
3. **Create a new branch**: Start a new branch for your changes
|
||||
```bash
|
||||
git checkout -b feature/your-feature-name
|
||||
```
|
||||
6. **Make your changes**: Implement the changes you wish to contribute.
|
||||
7. **Push your changes**: Upload your changes to your fork.
|
||||
```bash
|
||||
git push -u origin feature/your-feature-name
|
||||
```
|
||||
9. **Create a pull request**: Propose your changes to the main project.
|
||||
|
||||
|
||||
## Setting up your development environment
|
||||
|
||||
Documentation on how to setup a development environment is available here; https://docs.postiz.com/installation/development
|
||||
To contribute effectively, you’ll need to set up your development environment. Follow the instructions on this page: https://docs.postiz.com/installation/development
|
||||
|
||||
|
||||
Need Help?
|
||||
If you encounter any issues, please visit our [support page](https://docs.postiz.com/support) or check the community forums. Your contributions help make Postiz better!
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -31,6 +31,7 @@ COPY var/docker/Caddyfile /app/Caddyfile
|
|||
COPY .env.example /config/postiz.env
|
||||
|
||||
VOLUME /config
|
||||
VOLUME /uploads
|
||||
|
||||
LABEL org.opencontainers.image.source=https://github.com/gitroomhq/postiz-app
|
||||
|
||||
|
|
@ -55,6 +56,7 @@ COPY libraries /app/libraries/
|
|||
RUN npm ci --no-fund && npx nx run-many --target=build --projects=frontend,backend,workers,cron
|
||||
|
||||
VOLUME /config
|
||||
VOLUME /uploads
|
||||
|
||||
LABEL org.opencontainers.image.title="Postiz App (DevContainer)"
|
||||
|
||||
|
|
@ -70,6 +72,7 @@ COPY --from=devcontainer /app/libraries/ /app/libraries/
|
|||
COPY package.json nx.json /app/
|
||||
|
||||
VOLUME /config
|
||||
VOLUME /uploads
|
||||
|
||||
## Labels at the bottom, because CI will eventually add dates, commit hashes, etc.
|
||||
LABEL org.opencontainers.image.title="Postiz App (Production)"
|
||||
|
|
|
|||
|
|
@ -0,0 +1,44 @@
|
|||
# Security Policy
|
||||
|
||||
## Introduction
|
||||
|
||||
The Postiz app is committed to ensuring the security and integrity of our users' data. This security policy outlines our procedures for handling security vulnerabilities and our disclosure policy.
|
||||
|
||||
## Reporting Security Vulnerabilities
|
||||
|
||||
If you discover a security vulnerability in the Postiz app, please report it to us privately via email to one of the maintainers:
|
||||
|
||||
* @nevo-david
|
||||
* @jamesread ([email](mailto:contact@jread.com))
|
||||
* @jonathan-irvin ([email](mailto:offendingcommit@gmail.com))
|
||||
|
||||
When reporting a security vulnerability, please provide as much detail as possible, including:
|
||||
|
||||
* A clear description of the vulnerability
|
||||
* Steps to reproduce the vulnerability
|
||||
* Any relevant code or configuration files
|
||||
|
||||
## Supported Versions
|
||||
|
||||
This project currently only supports the latest release. We recommend that users always use the latest version of the Postiz app to ensure they have the latest security patches.
|
||||
|
||||
## Disclosure Guidelines
|
||||
|
||||
We follow a private disclosure policy. If you discover a security vulnerability, please report it to us privately via email to one of the maintainers listed above. We will respond promptly to reports of vulnerabilities and work to resolve them as quickly as possible.
|
||||
|
||||
We will not publicly disclose security vulnerabilities until a patch or fix is available to prevent malicious actors from exploiting the vulnerability before a fix is released.
|
||||
|
||||
## Security Vulnerability Response Process
|
||||
|
||||
We take security vulnerabilities seriously and will respond promptly to reports of vulnerabilities. Our response process includes:
|
||||
|
||||
* Investigating the report and verifying the vulnerability.
|
||||
* Developing a patch or fix for the vulnerability.
|
||||
* Releasing the patch or fix as soon as possible.
|
||||
* Notifying users of the vulnerability and the patch or fix.
|
||||
|
||||
## Template Attribution
|
||||
|
||||
This SECURITY.md file is based on the [GitHub Security Policy Template](https://github.com/github/security/blob/master/SECURITY.md).
|
||||
|
||||
Thank you for helping to keep the `postiz-app` secure!
|
||||
|
|
@ -361,6 +361,7 @@ html {
|
|||
|
||||
.uppy-ProgressBar-percentage {
|
||||
position: absolute;
|
||||
color: red;
|
||||
top: 50%;
|
||||
left: 50%;
|
||||
transform: translate(-50%, -50%);
|
||||
|
|
@ -383,4 +384,4 @@ div div .set-font-family {
|
|||
font-stretch: 100% !important;
|
||||
font-style: normal !important;
|
||||
font-weight: 400 !important;
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ export function Login() {
|
|||
</div>
|
||||
<div className="text-center mt-6">
|
||||
<div className="w-full flex">
|
||||
<Button type="submit" className="flex-1" loading={loading}>
|
||||
<Button type="submit" className="flex-1 rounded-[4px]" loading={loading}>
|
||||
Sign in
|
||||
</Button>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -198,7 +198,7 @@ export function RegisterAfter({
|
|||
</div>
|
||||
<div className="text-center mt-6">
|
||||
<div className="w-full flex">
|
||||
<Button type="submit" className="flex-1" loading={loading}>
|
||||
<Button type="submit" className="flex-1 rounded-[4px]" loading={loading}>
|
||||
Create Account
|
||||
</Button>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ const useFaqList = () => {
|
|||
return [
|
||||
{
|
||||
title: `Can I trust ${isGeneral ? 'Postiz' : 'Gitroom'}?`,
|
||||
description: `${isGeneral ? 'Postiz' : 'Gitroom'} is proudly open-source! We believe in an ethical and transparent culture, meaning Postiz will live forever. You can check the entire code / or use it for your personal use. You can check the open-source repository click here.`,
|
||||
description: `${isGeneral ? 'Postiz' : 'Gitroom'} is proudly open-source! We believe in an ethical and transparent culture, meaning that ${isGeneral ? 'Postiz' : 'Gitroom'} will live forever. You can check out the entire code or use it for personal projects. To view the open-source repository, <a href="https://github.com/gitroomhq/postiz-app" target="_blank" style="text-decoration: underline;">click here</a>.`,
|
||||
},
|
||||
{
|
||||
title: 'What are channels?',
|
||||
|
|
@ -18,7 +18,7 @@ const useFaqList = () => {
|
|||
isGeneral ? 'Postiz' : 'Gitroom'
|
||||
} allows you to schedule your posts between different channels.
|
||||
A channel is a publishing platform where you can schedule your posts.
|
||||
For example, you can schedule your posts on Twitter, Linkedin, DEV and Hashnode`,
|
||||
For example, you can schedule your posts on X, Facebook, Instagram, TikTok, YouTube, Reddit, Linkedin, Dribbble, Threads and Pinterest.`,
|
||||
},
|
||||
{
|
||||
title: 'What are team members?',
|
||||
|
|
|
|||
|
|
@ -188,7 +188,7 @@ export const Filters = () => {
|
|||
<div className="flex-1">{betweenDates}</div>
|
||||
<div
|
||||
className={clsx(
|
||||
'border border-tableBorder p-[10px]',
|
||||
'border border-tableBorder p-[10px] cursor-pointer',
|
||||
week.display === 'day' && 'bg-tableBorder'
|
||||
)}
|
||||
onClick={setDay}
|
||||
|
|
@ -197,7 +197,7 @@ export const Filters = () => {
|
|||
</div>
|
||||
<div
|
||||
className={clsx(
|
||||
'border border-tableBorder p-[10px]',
|
||||
'border border-tableBorder p-[10px] cursor-pointer',
|
||||
week.display === 'week' && 'bg-tableBorder'
|
||||
)}
|
||||
onClick={setWeek}
|
||||
|
|
@ -206,7 +206,7 @@ export const Filters = () => {
|
|||
</div>
|
||||
<div
|
||||
className={clsx(
|
||||
'border border-tableBorder p-[10px]',
|
||||
'border border-tableBorder p-[10px] cursor-pointer',
|
||||
week.display === 'month' && 'bg-tableBorder'
|
||||
)}
|
||||
onClick={setMonth}
|
||||
|
|
|
|||
|
|
@ -160,7 +160,7 @@ export const SettingsPopup: FC<{ getRef?: Ref<any> }> = (props) => {
|
|||
</div>
|
||||
</button>
|
||||
<button
|
||||
className="h-[24px] w-[88px] rounded-[4px] border-2 border-customColor21 flex justify-center items-center gap-[4px]"
|
||||
className="h-[24px] w-[88px] rounded-[4px] border-2 border-customColor21 hover:text-red-600 flex justify-center items-center gap-[4px]"
|
||||
type="button"
|
||||
>
|
||||
<div>
|
||||
|
|
@ -177,7 +177,7 @@ export const SettingsPopup: FC<{ getRef?: Ref<any> }> = (props) => {
|
|||
/>
|
||||
</svg>
|
||||
</div>
|
||||
<div className="text-[12px]" onClick={remove}>
|
||||
<div className="text-[12px] " onClick={remove}>
|
||||
Remove
|
||||
</div>
|
||||
</button>
|
||||
|
|
@ -191,7 +191,7 @@ export const SettingsPopup: FC<{ getRef?: Ref<any> }> = (props) => {
|
|||
</div>
|
||||
{!getRef && (
|
||||
<div className="justify-end flex">
|
||||
<Button type="submit">Save</Button>
|
||||
<Button type="submit" className='rounded-md'>Save</Button>
|
||||
</div>
|
||||
)}
|
||||
{!!user?.tier?.team_members && isGeneral && <TeamsComponent />}
|
||||
|
|
|
|||
Loading…
Reference in New Issue