vicjicama

Thanks for the feedback, is it cramped when it is vertical and horizontal? or just vertical I am only working on one wide screen size, I will take a look on how this looks on different screens

You have all the data on the left and the preview on the right, basically you can edit anything on the left side and it should be reflected on the preview size (you might need to refresh the preview on some changes).

- The cross-hairs in some elements will help you to navigate to the preview elements.

- You can click on the elements on the preview to go to the code, values, frame or page on the left side.

- You can add pages, products, categories and collections of products

- The pages are a little opinionated, those are composed by a list of elements, those elements can be a section, paragraph or raw code. (you can drag and drop the sections)

The editor and the preview are separated React apps. The cart functionality is provided by a React component, this same cart functionality will be present on the static production build. The main goal is to generate a static store that can be deployed to a CDN and only have server functionality when a order is placed

Hi!

I am working on an alternative service for the optimized images and deliver them over a CDN [1], for the images it generates a series of down-scaled images and provides a helper script to get the right image. Right now all the documentation and examples are focused on NodeJS [2], but I am working on examples for Dart, Ruby and Python.

Some of the features are:

- Optimized images - Custom domain - Public and Private files over a CDN - Upload widget, API, UI, dashboard and webhook - Bulk delete and bucket manipulation - CORS configuration

I am working on a couple features for the private files and image handling (based on the feedback from the users), let me know if you want to give it a try!

[1] https://bucket.listws.com [2] https://bucket.listws.com/docs/bucket/docs/intro

I did a couple fixes based on your comments, please let me know you feedback, thank you!

Another thing that I am planning is that you can download the result without register and free of charge

I haven't use webflow, I think that this is similar in the sense that both are web builders, but I am planning to combine/reuse this page editor with other services that I am working on. I was thinking also on offer a more opinionated builder based on predefined templates. Thanks for the feedback! I will work on those issues

Hi

I just wanted to share a tool that I am working on to edit HTML/EJS templates on the browser.

You can edit a EJS template and also the style, pre/post javascript and some page configurations.

I use it a lot on my projects for quick snips, I hope that this will be useful for you as well.

Let me know any feedback!

I got 84% for my site https://myraah.io/index.php/visualmind/report/aHR0cDovL3BhZ2...

I usually visit page performance sites to get some tips on things to improve on the performance, I think that this is a great idea to have a score on the appearance as well.

I got "You can further improve it by using better images and considering little denser layout." as a tip to improve, it would be great if there could be more details on the feedback.

I am working on www.pagews.com, it's a self service alternative, the static sites are based on the content of a spreadsheet/api and deployed to a CDN.

The site pagews.com is generated using the service for example (including capture forms back to the sheets).

I am using google spreadsheets to generate localized sites at www.pagews.com (The sheets for the site translations are public if you want to check an example)

The service convert the sheets to JSON and use them on the generated site content, I detect changes based on the hash for the cell and then the JSONs are published and versioned.

Hi

This is a tool to help you and your team to manage multiple SSH tunnels from/to an exist node.

I have been working a lot with microservices, containers and clusters lately and one thing that I did a lot is to open ssh tunnels to/from a test env to my lap or to help a co-worker to share his services to an exist node and them to my laptop, this was difficult once we started sharing multiple services to multiple developers that are working on multiple projects and multiple envs, this tool is to help us to manage all those interactions. I hope that this could be something useful for you and your team as well.

Some features/differences with other alternatives are:

- The tool is self hosted and free, you don't need to register or get a token.

- Share services from/to only the target devices without expose the service to the exit node.

- You can have the same port multiple times on you local machine. (super useful if you want to have the same hostname:port across the team devices or test environments).

- A GraphQL API to query and control (everything that you see/control on the UI) for easy automation and scripting.

- Aware of multiple devices, this makes the collaboration easier. A device can be your laptop, a RaspberryPI, a Kubernetes deployment, a node, etc...

- Save and control (Start/Stop) multiple endpoints per device.

- Split connection loads between multiple sshd instances/exit nodes to avoid slowness and instability. (For example to copy big files between devices/Shared docker registry/media streams)

- Independent SSH/SSHD services and configuration for the server and target devices.

Thank you and give it a try!, if you have any feedback or if you have any issue please let me know, I am happy to help.

The link is about the approach and the tools that I use as Fullstack(frontend/backend) working with stateless microservices in my local env.

I am using NodeJS/GraphQL/React(SSR) for my backend/frontend services.

The example is live, I version everything that goes to that cluster and it's opensource, this might be helpful as reference if you are using the same stack in containers.

I am using Kubernetes in the example, but the same approach apply to docker-compose, docker swarm, etc...

Let me know any feedback or comment. if you want to be in contact don't hesitate to reach out to [email protected]

I am very happy working with Kubernetes in a very small team, I really like the abstraction of the different entities and the declarative ways to configure them.

I think that the learning curve is not that steep if you already had to do the same than with Kubernetes with other alternatives, in my on experience I have been discovering a lot of features that are very helpful not just during production but also during the development environments that were a real pain before.

I am have a lab/cluster/blog running on Kubernetes, I am in charge of this one alone, it is opensource [1], I version everything that goes to the cluster so you can see the evolution of the kubernetes entities, the config, the containers and the code. I started this from scratch and improving it feature to feature, I think that this might be a big factor with my positive experience with Kubernetes.

I wonder if an issue with adopting kubernetes is to try to migrate a big system into kubernetes in a very limited time lapse and trying to push/force features as they were working/handled in the previous approach?

[1]: https://github.com/vicjicaman/microservice-realm

Thank you, I saw the example on the repository prom-grafana, I think that this example is for focus on the stand alone functionality of Tanka.

Do you know if there is an example or open source cluster using Tanka that I can try on minikube or a test cluster?

it would be really helpful to see how is the workflow to move from feature to feature, how are the envs when there is a bug, how do you replace the volume info from the cloud provider to minikube and all the considerations of the patched envs

Thanks for sharing, I will try it and give you feedback.

What I am doing for my env clusters is to have a versioned production yaml that acts as a source of truth, then if I need an env (regions, customer, dev, prod, feature, etc..) I take that source of truth, apply a transformation (usually a node script or bash... depending on the kubernetes entity) and then apply the resulting transformed yaml. Basically is: versioned production => transform => new env definitions

Do you have any recommendation/high level thoughts on how to integrate or substitute Tanka in this approach? Which are the downfalls that you see with this approach?

Thanks.

Hello

Yes, those are a lot, but that is on purpose. I am working on a tool to manage multiple repositories.

All those repositories were created to have the experience and experiment on how to manage and sync them all during the development or release of a feature.

I learned a lot working with all those repositories and how to overcome the drawbacks.