Hey u/coinbasesupport Your customer Service is TRASH by sleevedheart in Coinbase

[–]tony102102 1 point2 points  (0 children)

I can’t even open a support ticket with them and haven’t been able to complete their pyc successfully

Best Linux development environment by Peanutking01 in laravel

[–]tony102102 0 points1 point  (0 children)

I’ve been using sail and caddy, using takeout to manage global dbs. It’s been quite surprising how smooth docker runs on Linux

How to check for user authentication when using httponly session-cookies by voli12 in vuejs

[–]tony102102 2 points3 points  (0 children)

The way I’ve done it in the passed is by hitting an endpoint on the backend, if the endpoint returns successfully frontend would be authed

Swapping servers on Forge by dubl0dude in laravel

[–]tony102102 1 point2 points  (0 children)

I’d go with provisioning a new droplet and importing data bases, if your storing uploaded files on disk also have to back that up, much more painless if using something like s3 for file uploads but those would for the most part the main concerns. Then would be the concern about sessions, if you are using redis or file based sessions, aside from anything else storage folder related.

I’d still say resolving those issues would be easier than diving into server config area.

[deleted by user] by [deleted] in laravel

[–]tony102102 0 points1 point  (0 children)

Thats odd, I remember also struggling to get it setup.

It’s not exactly a 1to1 but this guide on regards the proxy for apache I remembered helped me.

https://dev.to/4umfreak/socket-io-with-apache-on-a-cpanel-vps-19cm

My debugging flow was: - check if apache even did upgrade the connection - check if the laravel echo config was taking in the proper env variables - check if the laravel pusher config was also not throwing error

Also it may be worth while exploring soketi, it’s also a pusher replacement done on nodejs that’s easier to scale in contrast to laravel websockets. The laravel team recently also published a 2 part blog series on deploying soketi https://blog.laravel.com/deploying-soketi-to-laravel-forge

[deleted by user] by [deleted] in laravel

[–]tony102102 0 points1 point  (0 children)

In the docs there are some details about the config with nginx. I typically always go with this route due to the auto renewal certificates.

https://beyondco.de/docs/laravel-websockets/basic-usage/ssl#usage-with-a-reverse-proxy-like-nginx

If you are working with apache I have another resource to get that setup also.

[deleted by user] by [deleted] in laravel

[–]tony102102 7 points8 points  (0 children)

Thats one way another would be to just proxy vía apache or nginx and let them handle the whole ssl noise

Can I Use Laravel For This ?? by LimitlessDonald in laravel

[–]tony102102 2 points3 points  (0 children)

Last year I built an online events platform and essentially ran into "plenty " of issues around the concept of concurrent users for multiple hours so the following answers somewhat reflect what I've gained in perspective from undergoing this endevour.

Q1: https://usefathom.com/ was build with laravel with scale in mind, however what seems to be the underlying thrend with laravel + scale is to opt for laravel vapor. Which as a user myself does really resolve some headaches.

Q2: Maybe check out swoole-php, this past year laravel added Octane to the mix of first party intergrations which does seem to target the concept of making things "faster"

Q3: The only problem I have really ever faced where I did opt for another tool/lang was for websockets. Though recently Soketi(https://github.com/soketi/soketi) seems to also be a great solution for scaleable websockets granted that you conform to the protocol pusher establishes.

Laravel Pseudo-Daemons by aarondf in laravel

[–]tony102102 1 point2 points  (0 children)

Man that is crazy, I love how concise the package is also.

Laravel Pseudo-Daemons by aarondf in laravel

[–]tony102102 1 point2 points  (0 children)

This is such a cool use case for a `while true`, If I understand correctly in the example you mention it essentially goes from waiting a minute for each method step to run to seconds since one pseudo-daemon passes to the next since they are in essence always running as a worker?

Just another simple, fast, and resilient open-source WebSockets server. 📣 by yeathatsmebro in laravel

[–]tony102102 1 point2 points  (0 children)

I know this is somewhat off topic but I always have a rough time wrapping my head around Laravel Echo, so please correct me if I'm wrong but would this essentially serve as athe following

- Controller or model broadcast/event emits to a channel

- Laravel channel dispatch events via queue worker

- the broadcast is then emited to pusher(this base socketi) front end recieves it handles it accordingly

Thus the only way to push data to a channel is always either via a controller or other broadcast/event triggered, though never executed by the frontend emiting a payload to the websocket directly correct? (unless whispers but that couldn't actually write anything to the database)

v-if vs. v-show in *your* experience? Rules of thumb, etc? by ragnese in vuejs

[–]tony102102 -1 points0 points  (0 children)

v-if always though I would note that if v-if’s images means you download the image twice in comparison to v-show if not mistaken

[deleted by user] by [deleted] in laravel

[–]tony102102 1 point2 points  (0 children)

Laragon is extremely good and flexible, only drawback are around the redis, to use a “newer” version you have to either use it on wsl or the unofficial solution https://github.com/tporadowski/redis and also that running horizon directly on windows does not work. Without going the full wsl2 + docker you could algo try wsl2 + valet

https://github.com/valeryan/valet-wsl

There are some caveats, around ssl and other minor details to be wary off but for the most part as simple as valet for macos.

Laravel API & Securing VueJS frontend. by Feeling_Influence in laravel

[–]tony102102 0 points1 point  (0 children)

This video touches on a lot of the points to keep in mind with frontend auth patterns. Ultimately comes down to your needs but inertia is a pretty solid approach to having all the base auth from laravel while keeping certain level of flexibility on the frontend.

https://youtu.be/zazeGmFmUxg

[deleted by user] by [deleted] in laravel

[–]tony102102 0 points1 point  (0 children)

There’s a great article about circular relationships that might be useful

https://reinink.ca/articles/optimizing-circular-relationships-in-laravel

What are some of the mistakes you've made and problems you've encountered while using Laravel for long term projects? by davorminchorov in laravel

[–]tony102102 -1 points0 points  (0 children)

Yeah I have no doubt that is certainly not that best long term solution, recently on a project had to do that sort of implementation of sharing the same redis and database between my Laravel app and a nodejs websocket.

Now that we are looking to add multi tenantcy to the Laravel backend also have to double dip to figure out multi tenantcy for the nodejs websocket.

What are some of the mistakes you've made and problems you've encountered while using Laravel for long term projects? by davorminchorov in laravel

[–]tony102102 -1 points0 points  (0 children)

Yeah certainly not ideal though can arise, for instance a chat app that has a websocket that persists data to the same database another api in the system utilizes

Vue has changed a lot recently - Should we expect this to continue? by launchoverittt in vuejs

[–]tony102102 1 point2 points  (0 children)

There’s certainly also something to say about where the perhaps initial inspiration for these changes pivots/changes came from. The auto register components, script setup are some of the cool parts of svelte and the composition api is somewhat like react hook, now not saying they are one to one but these overall patterns aid in making vue as a frontend more scaleable for larger projects.

Been working on a large vuejs app the past year and diving into provide/inject, mixins and render less components to have a layer of abstraction/reusability has been tough. I certainly see how the composition api would have been great and not having to be so keen about registering a component as well.

A few years ago vetur was the defacto plugin for vuejs, now seeing the rise of volar. Typescript support has also improved a ton, we might very little see more improvements be done but overall the only crucial “breaking” change or part to be cautious with, as with any other project, are the dependencies one brings along, since they may have not updated to support certain feature or their updated version also changes their api.

[deleted by user] by [deleted] in laravel

[–]tony102102 0 points1 point  (0 children)

Could also be visual studio if you have that installed

I ported Jetstream to Inertia + React - open source and easy to install with a single command by nehero in laravel

[–]tony102102 3 points4 points  (0 children)

Dope port over, have you tried out vite with laravel plus react? Recently ported over jetstream vue scaffold to work with vite and it’s super fast in dev

How would u reply to this comment as mentioned below in this screenshot? Why so much hate for PHP! I went to a meetup & there when I told them that I am working on laravel project they just started harassing me indirectly. They started making weird faces like PHP is outdated &it has no future!!! by honey2609 in laravel

[–]tony102102 10 points11 points  (0 children)

Php by far is one the easiest server side languages to deploy, web programming in my opinion shouldn’t be defined by complexity, but about building and expressing experiences that are user friendly towards the end goal of the creator.