Hi saleor team. In the last days We have seen in your git, that your dash and front repositories don't seem to went at the same speed that your django saleor api back. Have you published in some place the roadmap of saleor or future plans?
We saw these two PR mirumee/saleor#5000
and mirumee/saleor#5043
We were thinking in change from django version to the react storefront version, but we need to make some predictions according to your roadmap.
Thanks!
@rboixaderg Hey Roger! Thank you for your question and support. Our detailed roadmap is still under discussion. I'll keep you updated once it's ready. However, what I can tell is that we're working on a few important features such as multi-currency, CSV import/export, permission groups, multi-channel, and more. There is no exact release date for each function, but you can expect them in Q1 (at least some of them).
The new storefront is still in beta. We fix the bugs and add some small improvements for now. We don't maintain the old storefront anymore, so all the new updates will be available only on the react version. I'll inform you what we are planning to add to the storefront as soon as I know more details.
@/all When it comes to A/B testing, everything boils down to reducing guesswork and making decisions based on hard data. Read more about best practices that should bring results to your e-commerce business: http://bit.ly/ABTesting_article
And what are your best practices for A/B testing? Do you run them often? It would be great if you could share your thoughts with us. We'd love to hear and discuss your experience!
@karolkielecki What would be the recommended setup and configuration to deploy the Saleor Dashboard 2.0? We have the GraphQL API deployed on AWS EBS Docker container. Should Dashboard be in its own separate server or better to have both in the same server or is it better to be deployed on some static host like S3?
PS: I'm more of a developer than devops guy.
This is the Dockerfile
FROM node:10 as builder
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
ARG APP_MOUNT_URI
ARG API_URI
ARG STATIC_URL
ENV API_URI http://saleor20-cabinets-dev.us-west-2.elasticbeanstalk.com/graphql/
ENV APP_MOUNT_URI ${APP_MOUNT_URI:-/dashboard/}
ENV STATIC_URL ${STATIC_URL:-/dashboard/}
RUN STATIC_URL=${STATIC_URL} API_URI=${API_URI} APP_MOUNT_URI=${APP_MOUNT_URI} npm run build
FROM nginx:stable
WORKDIR /app
COPY ./nginx/default.conf /etc/nginx/conf.d/default.conf
COPY --from=builder /app/build/ /app/Saleor 2.9.1 SECURITY release
@/all We've rolled out a new release that fixes a vulnerability issue in Saleor. The fixes are available on Saleor 2.9.1 and the master branch. If you use 2.9.0 or older version, please update Saleor as soon as possible.
Check out more details here: https://github.com/mirumee/saleor/releases/tag/2.9.1
I am trying to implement saleor (from the beginning) with git submodules, help me to know if this is a correct way..
sorry maybe I need to be very explicit
initial setup
git remote rename origin fork //remane my origin reference as "fork"git remote add origin https://github.com/mirumee/saleor.git//add saleor as "origin"
With the fork already made i create two branches (dev & prod)
My team will work against the dev branch and it will receive the ascending changes by the master brach. Logically, the prod branch is for deploy proposess, but it this will merged against the dev branch.
Also the master branch receive the ascending changes for saleor "origin".
In the dev branch i create submodules. pull , commit & ,push (on fork reference) the changes. This is when you have to really start being careful with send correclty this changes.
`*fork saleor
|
|
|_>submodule dashboard
|
|_>submodule storefront
` Follow this way, the master branch is outdated respect to dev...this is not a problem for my workflow ...or yes?
What is the best way to handle it?
on branch (master)git status
On branch master
Your branch is up to date with 'fork/master'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
saleor-dashboard/
saleor-storefront/Thanks for your time...
https://github.com/mirumee/saleor/releases/tag/2.9.1
DEBUG:True
AWS_ACCESS_KEY_ID = "aws-access-key-id"
AWS_MEDIA_BUCKET_NAME = "name-of-the-bucket"
AWS_QUERYSTRING_AUTH = False
AWS_S3_REGION_NAME = "us-west-1"
AWS_SECRET_ACCESS_KEY ="secret-access-key"
AWS_DEFAULT_ACL =None
S3_URL = '//%s.s3.amazonaws.com/' % AWS_MEDIA_BUCKET_NAME
MEDIA_URL = S3_URL + 'media/'
MEDIA_ROOT = MEDIA_URL